-
-
Notifications
You must be signed in to change notification settings - Fork 86
Add Support for PHPCS Standards / Rulesets and Related Bug Fixes #216
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
Closed
Kenneth-Sills
wants to merge
7
commits into
easy-coding-standard:main
from
Kenneth-Sills:kesills-phpcs-standards
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
0f89875
chore: add a test script to composer for convenience
Kenneth-Sills 006eb09
docs: adding docs for upcoming features
Kenneth-Sills b35dcb0
fix(caching): improve reliability of configuration caching
Kenneth-Sills 3346b3a
fix(phpcs): stop reporting duplicate unfixable errors with fixable ch…
Kenneth-Sills 7493fdf
fix(phpcs): respect sniffers requesting to be disabled during file pr…
Kenneth-Sills 090d8fd
feat(phpcs): added support for standard imports and sniffer warnings.
Kenneth-Sills c615460
refactor(phpcs): renamed a variable for clarity after its semantics w…
Kenneth-Sills 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Hey, thanks for many contributions 🥳
Let's take it one by one to ship them faster :)
I like this feature - please separate it to own PR 👍
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.
Sure thing!
Just so we're on the same page, do you just want me to pull out the
with[out]Warnings
methods/parameters with warnings disabled by default, then enabled when usingwithSnifferStandards
?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.
Thanks 👍
Lets start with warnings as a standalone feature. Without any dependency on
withSnifferStandards
.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.
Sorry for the delay, been focused on "work" work! I'll be able to get back to this soon, and I'll create
fourfive separate PRs for (in this order):test
Script #227.I'll make sure each is appropriately tested, of course. I'll then rebase this branch and force merge to my fork. Hopefully that'll cut down on the effort required to review these submissions.😄
Let me know if you're opposed to the plan above or have any suggestions. Thanks for your time!
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.
4/5 of the above have been prepared and are ready for your review! The last changes to allow PHPCS warnings has dependencies on the others though, so I'll need to wait for those PRs to be merged before coming back to finish it.
I appreciate your time, Tomas! Sorry again for taking so long. 😭
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.
Hey, Tomas! Don't mean to be a bother, but is there any chance we could take a look at some of those above PRs?
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.
Since it's been a while, I'll need to revisit the PHPCS warnings support feature to see what needs to be done to support it. 😅