patternfly / patternfly/patternfly-doc-core
Add versioning suppport for the tokens API
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 11
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 1
Description
NEEDS REFINEMENT
Followup to #203
The solution implemented in #203 doesn't support importing different versions of tokens.
We need to enable consumers to specify the versions of design tokens they would like to expose, supply those versions, and properly filter output via the api routes, i.e. return all v5 tokens on the /v5/tokens endpoint, and no v6 versions.
Jira Issue: PF-3463
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 reviewing the implementation from #203 and tracing the token import flow and API routes described in this issue. Define how consumers specify exposed token versions, then verify that /v5/tokens returns v5 tokens and excludes v6 tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100