Mark properties as required when it makes sense.
Open
Nobody has claimed this yet.
enhancement
specification
- Dominant language
- Go
- Stars
- 323
- Forks
- 133
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 2
Description
We should mark properties in the definitions as required when it's necessary. That way the generator will create validations for all the POST endpoints to verify those fields in the client side.
See the simple model example: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#simple-model
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 definitions and the linked OpenAPI simple model example, then trace how the generator handles POST endpoints and client-side validations. Done means the necessary properties are marked as required and the generator creates validations for those fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100