Make reducer builder closure parameters explicit #1897
Merged
Conversation
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
- Scope(...:child:) - forEach(...:element:) The one exception is `CombineReducers`, which already includes the `Reducers` in its name.
mbrandonw
approved these changes
Feb 9, 2023
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.
While this is a breaking change, its impact is likely pretty low, as trailing closure syntax should be overwhelmingly preferred in usage, and Xcode should provide automatic migration to the new parameter names:
Scope(...:child:)forEach(...:element:)The one exception that still is nameless is
CombineReducersbecause it already includes theReducersin its name, and a parameter name comes across redundant/verbose.