Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Named parameters rule #25

Merged
merged 2 commits into from Jul 11, 2023
Merged

Named parameters rule #25

merged 2 commits into from Jul 11, 2023

Conversation

juanpcapurro
Copy link
Contributor

@juanpcapurro juanpcapurro commented Jul 3, 2023

should close #7

I'd like @DrakeEvans feedback since you reported it, and @PaulRBerg 's since I have seen you be very vocal about using named function parameters 馃檭

@juanpcapurro juanpcapurro linked an issue Jul 4, 2023 that may be closed by this pull request
@juanpcapurro juanpcapurro force-pushed the named-parameters-rule branch 4 times, most recently from 3f69e41 to 91048dc Compare July 10, 2023 17:27
@juanpcapurro juanpcapurro marked this pull request as ready for review July 10, 2023 18:09
@PaulRBerg
Copy link
Contributor

Not able to review RN but I'm absolutely in favor of such a rule - I'd apply it everywhere

I need to change the behaviour of how a value of 0 is interpreted in the
config and I need to make sure I don't break the behaviour of other
rules in the process.
@juanpcapurro juanpcapurro merged commit 727ec72 into master Jul 11, 2023
10 checks passed
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.

[Request] New rule for using named function parameters
2 participants