[APIView] Evaluate if we should update API Spec revision when there is a new version of the swagger/typespec parser
Open
APIView
Central-EngSys
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Currently only token files are stored in APIView, so when there is a new parser version, APIView can't re-generate the revisions.
- Is this a scenario we should cover?
- If we do this, there will be an increased execution time when updating all the revisions. By how much? is this ok?
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing APIView's token storage and revision-generation flow, then determine how parser-version updates would trigger regeneration and measure the effect of updating all revisions. Done means the support decision, execution-time impact, and acceptable behavior are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100