feat: make format compatible with "PER Coding Style 2.0" #2269
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
|
Hi @czosel can you take a look a this PR? |
|
I want to make this change, I look at the PRs and I realise that I'm 5 days late... Thanks @ferchoz ;) |
ferchoz
changed the title
Improved! |
|
@czosel can you take a look at it? thanks!! |
czosel
force-pushed
the
feature/make-format-compatible-with-phpcsfixer
branch
from
b8128f5
to
9fe6fd5
Compare
|
Released in |
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.
This change allows to use this plugin along with "PER Coding Style 2.0"
formating :
readonly final class ClassName {}to
final readonly class ClassName {}doc:
https://www.php-fig.org/per/coding-style/#46-modifier-keywords