Skip to content

fix: support literal query string#2590

Merged
mikicho merged 3 commits intomainfrom
Michael/fix-query-string
Feb 17, 2024
Merged

fix: support literal query string#2590
mikicho merged 3 commits intomainfrom
Michael/fix-query-string

Conversation

@mikicho
Copy link
Copy Markdown
Member

@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.

Michael Solomon added 2 commits February 16, 2024 17:57
Copy link
Copy Markdown
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
@mikicho mikicho deleted the Michael/fix-query-string branch February 17, 2024 18:38
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 13.5.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Dec 4, 2024

🎉 This PR is included in version 14.0.0-beta.19 🎉

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.

encodedQueryParams example throws Argument Error

2 participants