make sure we have tests for new design tokens functionality
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
### Find where we need to add tests
- [ ] Document new design tokens functionality that isn't being tested in tasklists on this issue
### `tokens/utils.js`
- [ ] `findTokenByPath`
- [ ] `annotateReferencedTokenExtensions`
- [ ] `processAndUpdateTokens`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading tokens/utils.js and the implementations of findTokenByPath, annotateReferencedTokenExtensions, and processAndUpdateTokens. Locate the existing tests for this utility area, identify the new design-token behavior that lacks coverage, and document any additional uncovered functionality in the issue tasklist. Done means the named functionality has meaningful test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100