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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CS: function naming consistency #52

Merged
merged 1 commit into from
Mar 13, 2018
Merged

Conversation

jrfnl
Copy link
Contributor

@jrfnl jrfnl commented Feb 10, 2018

Historically, this library uses camelCaps for function names instead of the WP convention of using snake_case.

There is no need to change this, we just need to allow for it and fix up the one exception to the rules (and allow for one more, but that will be handled via the PHPCS ruleset).

As this involves a public method, this can be considered a BC-break. However, the reason for the method to be public is that it is hooked in via add_action(), not because it is a method which external parties are expected to call on, so I expect the BC-break to be theoretical and not to have any impact in practical terms.

Historically, this library uses `camelCaps` for function names instead of the WP convention of using `snake_case`.

There is no need to change this, we just need to allow for it and fix up the few exceptions to the rules.
@jrfnl jrfnl requested a review from moorscode February 10, 2018 21:37
@jdevalk jdevalk merged commit df8bda8 into master Mar 13, 2018
@jdevalk jdevalk deleted the JRF/CS/function-name-consistency branch March 13, 2018 19:19
@jrfnl jrfnl added this to the Next release milestone Mar 14, 2018
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.

3 participants