-
Notifications
You must be signed in to change notification settings - Fork 136
[BUG] Support for deepObject for query parameters #320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @alextarrago Actually, your swagger file is not valid. Referenced parameters should be parameter, not just model. I mean parameters should have "in", "required" field and should NOT have properties. If you put such parameter into swagger editor you will have next error:
Please, share valid yaml code. Also, I can fix you swagger, for example, in a next way: Everything is clear here? Am I understand you problem correctly? |
Hi @Vovanella95, thanks for the fast reply! Thanks. |
@alextarrago OK I have generated your example. I have request with parameter ServiceCategoryCriteria. What is the issue? I can't understand what is wrong
|
@alextarrago closing the issue due to no response. Please reopen it if it actual |
Hi @Vovanella95 , similar to this OAI/OpenAPI-Specification#1706, parameters:
- name: filter
in: query
schema:
type: object
style: deepObject
explode: true
description: Filter by category ID The query param generated from this _cmsRemoteDataSource.subCategoriesGet(
filter: {r'[category][id][$eq]': 25},
) is |
Support for deepObject notation for query parameters.
This spec does not generate the expected behaviour.
Intercepting the parameters in the client interceptor gives us the following code:
{q: Instance of 'ServiceCategoryCriteria'}
Some guidance on here? :)
The text was updated successfully, but these errors were encountered: