interagent / interagent/committee
Add support for multiple versions to middleware
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 955
- Forks
- 145
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 6
Description
I love the idea of having middleware in place to check request and response data, but it doesn't appear that they support multiple versions. The middleware take a schema option, but if you have multiple versions this schema won't be known ahead of time and you have to choose one. (I started adding directories to represent versions to docs/schema -- is this proper?) What do y'all think about this?
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 middleware's schema option and the existing docs/schema directories, including the version directories mentioned in the issue. Read the current request and response validation entry points and the discussion to determine the intended version-selection behavior. Done means middleware can support multiple schema versions with documented, agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100