server versioning story
- Dominant language
- TypeScript
- Stars
- 719
- Forks
- 33
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 60
Description
**Is your feature request related to a problem? Please describe.**
A common practice in REST-style APIs is to use a header (e.g. `x-api-version`) to specify which API version you want to use.
For feTs server, we should think about how we can serve/satisfy multiple API versions with a single server/router.
**Describe the solution you'd like**
Happy path documented and if required the necessary API adjustments within feTS.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by examining the feTS server and router documentation to determine how requests are currently versioned; done would require a documented happy path for serving multiple API versions and any agreed API adjustments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100