interagent / interagent/committee
OpenAPI 3: "attribute does not allow null values" in ResponseValidation
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 955
- Forks
- 145
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 6
Description
I have a property in a response defined as:
filename:
nullable: true
type: string
but when empty:
{"id":"invalid_response","message":"...properties/filename does not allow null values"}
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 the ResponseValidation entry point and trace how the shown OpenAPI 3 schema is checked when filename is null. Reproduce the reported error with the nullable string property, then confirm that a null filename is accepted without changing validation for non-null values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100