chore: use consistent parameter names #29361
Merged
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
codebytere
approved these changes
May 31, 2021
electron-cation
bot
added
new-pr 🌱
zcbenz
approved these changes
Jun 1, 2021
|
No Release Notes |
This was referenced Jun 1, 2021
|
I have automatically backported this PR to "14-x-y", please check out #29441 |
|
I have automatically backported this PR to "13-x-y", please check out #29442 |
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.
Description of Change
Another PR like #26162. Aims to keep parameter names consistent between declaration and definition. Some of them are judgement calls, where I tended to go with the path of least resistance which was change the name in the declaration.
Checklist
npm testpassesRelease Notes
Notes: none