Support custom rules #55
Closed
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.
Hey pinters,
I wanted to use a linter since forever, however wasn't really satisfied with PHP-CS-Fixer as a standalone package. I wouldn't be able to use it out of the box either way because I use a unique – malicious gossip has it that it's a weird – coding style.
Anyway, now with pint I just got to implement a linter. This PR is my attempt to implement custom rules, so I can start writing my own and use them with pint.
The configuration now accepts a new property where the fixers FQCN and the name of the rule can be specified:
The key is the FQCN to the fixer class and the value is the rule name which should be used for the configuration. I added two tests:
custom
property can be read by theConfigurationJsonRepository
I don't know if custom rules are even a desired feature for pint and if this gets closed I will still be waiting excitedly for custom rules. However, I'd love to hear some thoughts on this. 🙃