New Universal.UseStatements.NoLeadingBackslash sniff
#46
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
jrfnl
force-pushed
the
feature/new-usestatements-no-leading-backslash-sniff
branch
4 times, most recently
from
f7acef1
to
d66e4b4
Compare
New sniff to verify that a name being imported in an import use statement does not start with a leading backslash. Names in import `use` statements should always be fully qualified, so a leading backslash is not needed and it is strongly recommended not to use one. This sniff handles all types of import use statements supported by PHP, in contrast to any of the other sniffs for the same in, for instance, the PSR12 or the Slevomat standard, all of which are incomplete. Includes fixer. Includes unit tests. Includes documentation. Includes metrics.
jrfnl
force-pushed
the
feature/new-usestatements-no-leading-backslash-sniff
branch
from
d66e4b4
to
1fbc526
Compare
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.
New sniff to verify that a name being imported in an import use statement does not start with a leading backslash.
Names in import
usestatements should always be fully qualified, so a leading backslash is not needed and it is strongly recommended not to use one.This sniff handles all types of import use statements supported by PHP, in contrast to any of the other sniffs for the same in, for instance, the PSR12 or the Slevomat standard, all of which are incomplete.
Includes fixer.
Includes unit tests.
Includes documentation.