swagger-api / swagger-api/swagger-codegen
Client-generation: Allow data validation on the client side (using minLength/maxLength)
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Currently the generated Java-clients perform required-validation automatically.
Do you think this makes sense for minLength/maxLength as well, to reject the request on the client side before sending to the server?
For Java the JSR-303 Bean Validation API could be used for this automatically.
For other languages maybe a JSON-schema validation could be used.
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 how generated Java clients currently perform required validation, then compare the proposed JSR-303 Bean Validation approach with JSON-schema validation for other languages. The issue does not name files or tests; done would require an agreed validation design and implementation scope for minLength/maxLength across the affected client generators.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100