interagent / interagent/committee
OpenApi 2.0 "Committee: no name section in link data" when parameter is using a reference
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 955
- Forks
- 145
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 6
Description
I'm trying to load specs located here. I'm working from a local version and I had to remove a couple unsupported "format" tags. But once I do that, I get an ArgumentError for Committee: no name section in link data. Digging in it's failing in the ParameterSchemaBuilder because it's checking
"parameters": [
{
"$ref": "#/parameters/authorization"
}
]
and not seeing a name key for check_required_fields!.
Looking at the code there's no place before that point that would fill the reference, so I don't know if it should pass the check or if there should be some translation before that point. Or maybe I misunderstood how 2.0 is allowed to use references?
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 with ParameterSchemaBuilder and the check_required_fields! call described in the issue, then inspect how the linked OpenAPI 2.0 specification resolves the parameter reference. Compare the referenced parameter object with the inline parameter handling and determine whether reference resolution should occur before validation. Done means the supplied specification loads without the ArgumentError while preserving required-field validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100