Add "encodeParams" option to rtkq-codegen-openapi #4568
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit a989ed9:
|
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
7 tasks
b8f872e to
20bcc26
Compare
|
Seems reasonable, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces a new
encodeParamsoption to the Redux Toolkit Query (RTKQ) OpenAPI code generator. When enabled, this option will automatically applyencodeURIComponentto the generated query parameters, ensuring that special characters in query strings are correctly encoded.This feature will be useful for users who need to ensure their query parameters are URL safe, particularly in cases where special characters are commonly used.
Fixes #3822
This PR:
encodeParamsoption to automatically perform URL safe encoding to the generated query and path parametersencodeParamsoptionflattenArgtest case which was not passing due to formatting