Updated URL query encoding to not use a deprecated function #583
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
fadyyecob
changed the title
fadyyecob
changed the title
fadyyecob
changed the title
Deus-92
approved these changes
Oct 10, 2022
Not sure what you mean by this @Deus-92 , it doesn’t seem to be needed. Are you able to merge the pr btw? |
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.
Used
stringByAddingPercentEncodingWithAllowedCharacterswithURLQueryAllowedCharacterSetas the allowed character set for encoding key/value pairs sent over the URLRequest. And subtracted the characters from it that it should also encodeRelated issue: #141