Drew Powers

This is a great idea, and I’d be in favor of adding it. [msw has a similar concept](https://mswjs.io/docs/basics/mocking-responses/#using-httpresponse-class) where there are reasons why you’d have a custom Request or Response...

Would also love to see this land 🙏

If the spec supported a [$deprecated property](https://github.com/design-tokens/community-group/issues/118) would that be sufficient?

Or, alternatively, if you read that issue some people have more advanced requirements of organizing their tokens, and they may have additional designations other than “deprecated.” What if we allowed...

Good point. I guess that just leaves 2 questions: 1. Does this make sense to ignore tokens globally (i.e. for all outputs?) 2. Are there cases where you’d want to...

True—breaking changes don’t matter much in pre-1.0. But I think the API / usability is everything, and I do think sweating the details matter! I should have put more emphasis...

So `v0.1.0` does somewhat solve this in that it creates unions of “good” and “bad” types. Theoretically, now, if you have different schemas for different error codes (like different shapes...

Update on this: the `response.status` discriminator support still hasn’t been added, and this issue will be complete once that’s in.

I’m not opposed to that. Though HCT off the bat hasn’t performed clearly better than OKLAB/OKLCH (not to mention OKLAB/OKLCH support has landed in all modern browsers but the path...

Will take a look. I think in the Slack one, that can be fixed as we can just prevent `[key: string]: Record` from being generated—that’s just noise (that should only...