Description
What is a problem?
In
only the operation.parameters is passed to the operation builder, while the OpenAPI spec also supports specifying parameters
at the path level that are shared by all operations for that path.
Considering that the method (under which an operation is keyed in the spec) is passed to the operation builder, it looks like the Operation instance is supposed to contain all information for itself, which should include the path parameters.
Describe the solution you'd like
Pass the extracted path parameters down to the operation builder, and have the operation builder do the resolution. Operations may override the path parameters according to the spec, but they cannot remove them. Note that a parameters is uniquely identified by the combination of name and location, so you can use those as dict keys for the override-behaviour check.
Describe alternatives you've considered
I can do the processing in my code of course, but ideally the code making use of openapi3-parser should not have to think about all the intricacies of the OpenAPI 3 specification.
Additional context
I'd like to be able to look at a single Operation instance and have all the necessary information at hand.
I'd also suggest including the URL path in the builder for that reason.
If you're open to this, then I can definitely submit a PR :-)