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

fix(execute): parse stringified objects #3474

Merged
merged 3 commits into from
Apr 23, 2024
Merged

fix(execute): parse stringified objects #3474

merged 3 commits into from
Apr 23, 2024

Conversation

glowcloud
Copy link
Contributor

Refs swagger-api/swagger-ui#7734

This example from the test:

requestBody: {
  a: {
    b: 'c',
    c: ['d', 'e'],
    d: {
      e: 'f',
    },
  },
},

will return:

a%5Bb%5D=c&a%5Bc%5D=%5B%22d%22%2C%22e%22%5D&a%5Bd%5D=%7B%22e%22%3A%22f%22%7D

which should decode to:

a[b]=c&a[c]=["d","e"]&a[d]={"e":"f"}

As established for previous issues, we're not encoding nested objects/arrays, as the behaviour for that is undefined.

@char0n char0n merged commit c4ff9a2 into master Apr 23, 2024
6 checks passed
@char0n char0n deleted the content-deep-object branch April 23, 2024 08:10
swagger-bot pushed a commit that referenced this pull request Apr 23, 2024
## [3.27.1](v3.27.0...v3.27.1) (2024-04-23)

### Bug Fixes

* **execute:** parse stringified objects ([#3474](#3474)) ([c4ff9a2](c4ff9a2))
@swagger-bot
Copy link
Contributor

🎉 This PR is included in version 3.27.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants