-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
[Documentation] PSR12 - Constant Visiblity #238
Merged
jrfnl
merged 4 commits into
PHPCSStandards:master
from
dingo-d:documentation/PSR12-properties-constant-visibility
Jan 13, 2024
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
25 changes: 25 additions & 0 deletions
25
src/Standards/PSR12/Docs/Properties/ConstantVisibilityStandard.xml
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
<documentation title="Constant Visibility"> | ||
<standard> | ||
<![CDATA[ | ||
Visibility must be declared on all class constants if your project PHP minimum version supports class constant visibilities (PHP 7.1 or later). | ||
]]> | ||
</standard> | ||
<code_comparison> | ||
<code title="Valid: Constant visibility declared."> | ||
<![CDATA[ | ||
class Foo | ||
{ | ||
<em>private</em> const BAR = 'bar'; | ||
} | ||
]]> | ||
</code> | ||
<code title="Invalid: Constant visibility not declared."> | ||
<![CDATA[ | ||
class Foo | ||
{ | ||
<em></em>const BAR = 'bar'; | ||
jrfnl marked this conversation as resolved.
Show resolved
Hide resolved
|
||
} | ||
]]> | ||
</code> | ||
</code_comparison> | ||
</documentation> |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it "class constants" ? Or all OO constants ? Constants can also be declared on interfaces, traits (PHP 8.2+) and enums, after all.
Also not sure if the "class" needs to be repeated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, the documentation states
That's why I opted to use that term.
I added the 'class' to distinguish them from
define
d constants.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fully understand (and support) why it was added, I just wonder if the right term was added. After all, the PSR12 definition is not available from within the PHPCS docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added this to the documentation description, I think it should help to avoid misunderstandings.