Skip to content

fix(utils): properly url encode all params #15

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

Merged
merged 1 commit into from
Oct 3, 2023
Merged

fix(utils): properly url encode all params #15

merged 1 commit into from
Oct 3, 2023

Conversation

tuky
Copy link
Contributor

@tuky tuky commented Sep 27, 2023

To fix #14.

@tuky
Copy link
Contributor Author

tuky commented Sep 27, 2023

BTW, I'm well aware this is actually a backwards incompatible change and should be released as a new major version. But I am pretty sure, this library is meant to be used without manually URL encoding parameters before passing them to your client.

@daolf daolf requested a review from kirby81 September 27, 2023 21:02
@kirby81 kirby81 self-assigned this Oct 3, 2023
Copy link
Contributor

@kirby81 kirby81 left a comment

Choose a reason for hiding this comment

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

Hi there,

Definitely a better solution to handle parameters and yes you're right this library is meant to be used without manually URL encoding parameters.

Thanks for your contribution, I will tag this as a new major version (2.0.0).

@kirby81 kirby81 merged commit 20b72df into ScrapingBee:main Oct 3, 2023
@tuky tuky deleted the patch-1 branch October 4, 2023 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not properly escaping params
2 participants