-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
feat: Add intentional nil encoding strategy to URLEncodedFormEncoder #3977
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
Open
darkbrewx
wants to merge
2
commits into
Alamofire:master
Choose a base branch
from
darkbrewx:feat-nil-encoding-dual-strategy
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This behavior can't change either. Instead it needs to default to the current behavior and only use the new behavior if the user provides the
encodeIfPresentclosure.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for pointing this out.
From my perspective, the current behavior remains fully backward-compatible.
encodeIfPresentEncodingandencodeEncodingclosures are equivalent.nilEncoding.encodeNilIfPresent()can fall back tonilEncoding.encodeNil()automatically.Implementing it as you suggested would require to:
encodeIfPresentEncodingtooptional, and when using single-parameter initializer, set it asnil.encodeIfPresentEncodingasfileprivateor introducing an additionalfileprivate(wider than private) flag to check fornil; otherwise, cannot directly unwrap it usingif let.So, may I ask you whether the current implementation is acceptable? Or if you have any further concerns, please let me know.