Re: [community-group] Add format schema (#360)

> Ah so we have a pnpm workspace. In the root level there’s no test framework, but inside `www/` there is Vitest configured (if you rebase off latest `main`; I forget when it was merged in). For tests in `public` I’d recommend just adding a new `www/tests` folder they can run from, that way we don’t deploy our tests to the website 😄. They should get picked up automatically, but if not, it’s just modifying Vitest’s [include](https://vitest.dev/config/include.html) option.
> 
> I do think the tests are optional—if you have some that are ready, or they wouldn’t take much time, we’d love to add them! But I don’t want to make this PR blocking. I tested it again and it works great 🙂

Ah right I didn't think of looking in the main branch 😅.
Maybe it would actually make sense to contribute the tests in a follow up PR. I created quite a lot of fixtures (about 4200 lines) and I think it might be easier to review if it is a separate PR? 
Maybe that could also give room for them to be considered more broadly. Not only as something that is being used to test the JSON schema but also as something that can be provided to design token tool makers to test their tools against as discussed in #247.

Also from our conversation in #356 I was not sure wether I should contribute the resolver schema that I had created, since you have already worked on one. Did you want me to contribute that one too?

-- 
GitHub Notification of comment by dgtlntv
Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/360#issuecomment-3645947660 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 12 December 2025 10:43:45 UTC