Skip to content
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

openapi3filter: deepObjects with the same properties conflict #946

Closed
MateusFrFreitas opened this issue May 3, 2024 · 0 comments · Fixed by #947
Closed

openapi3filter: deepObjects with the same properties conflict #946

MateusFrFreitas opened this issue May 3, 2024 · 0 comments · Fixed by #947

Comments

@MateusFrFreitas
Copy link
Contributor

MateusFrFreitas commented May 3, 2024

Before #923 a query with more than one deepObject worked just as expected. Now DecodeObject is ignoring the property's name.

Example:

- in: query
  name: obj
  required: false
  schema:
    type: object
    properties:
      prop:
        type: string
    required:
      - prop
  style: deepObject
  explode: true
  
- in: query
  name: obj2
  required: false
  schema:
    type: object
    properties:
      prop:
        type: string
    required:
      - prop
  style: deepObject
  explode: true

When parsing this url: http://localhost?obj[prop]=value both obj and obj2 receive value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant