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: support literal query string #2590

Merged
merged 3 commits into from Feb 17, 2024
Merged

fix: support literal query string #2590

merged 3 commits into from Feb 17, 2024

Conversation

mikicho
Copy link
Contributor

@mikicho mikicho commented Feb 16, 2024

closes #2342

@gr2m I'm a bit puzzled here. In the example, it seems like we support this, but we have (an old) test that specifically forbids string as an argument.

Anyway, I think we should support string.

Copy link
Member

@gr2m gr2m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to understand the origin of the test expecting interceptor.query('foo=bar') to throw an error and yeah, no idea. I agree with your assessment

@gr2m gr2m changed the title Support literal query string fix: support literal query string Feb 17, 2024
@mikicho mikicho enabled auto-merge (squash) February 17, 2024 18:36
@mikicho mikicho merged commit 4162fa8 into main Feb 17, 2024
23 checks passed
@mikicho mikicho deleted the Michael/fix-query-string branch February 17, 2024 18:38
Copy link

🎉 This PR is included in version 13.5.3 🎉

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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

encodedQueryParams example throws Argument Error
2 participants