interagent / interagent/committee
Can enum values be validated on a request ?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 955
- Forks
- 145
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 6
Description
On a request, request format can be validated by Committee::Middleware::RequestValidation.
But enums definition looks like not be validated by that.
I think it is useful to be validated because application code have not implement it like duplication.
Can we do that with some option ?
I checked enums mismatch on request won't raise exception with:
- Ruby 3.2.2
- Committee 5.0.0
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 at Committee::Middleware::RequestValidation and reproduce the enum mismatch described with Ruby 3.2.2 and Committee 5.0.0. Trace how request formats are validated and determine the intended option or behavior for enum definitions. Done means enum mismatches are validated without requiring duplicated application code, with the behavior covered by tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100