You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will result in an error for having an opening brace in a new line, at function declaration level
Opening brace should be on the same line as the declaration
While this should be checked by either Generic.Functions.OpeningFunctionBraceKernighanRitchie (included in this WP standard set), or Generic.Functions.OpeningFunctionBraceBsdAllman already.
It took me a few hours to figure this out, as I tried to exclude the rule Generic.Functions.OpeningFunctionBraceKernighanRitchie yet still see the error.
Yes, I am aware that this is the standard sets for WordPress, thus the "standard" should be having the opening brace in the same line with the function declaration, but I think this might be a bug. Please correct me if I'm wrong, because I'm totally new to this.
The text was updated successfully, but these errors were encountered:
https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/blob/cca93a6713881c684e38c1a226ea64944e5ddf1a/WordPress/Sniffs/WhiteSpace/ControlStructureSpacingSniff.php#L98
This will result in an error for having an opening brace in a new line, at function declaration level
Opening brace should be on the same line as the declaration
While this should be checked by either
Generic.Functions.OpeningFunctionBraceKernighanRitchie
(included in this WP standard set), orGeneric.Functions.OpeningFunctionBraceBsdAllman
already.It took me a few hours to figure this out, as I tried to exclude the rule
Generic.Functions.OpeningFunctionBraceKernighanRitchie
yet still see the error.Yes, I am aware that this is the standard sets for WordPress, thus the "standard" should be having the opening brace in the same line with the function declaration, but I think this might be a bug. Please correct me if I'm wrong, because I'm totally new to this.
The text was updated successfully, but these errors were encountered: