Fix some psr12 coding styles #19
Merged
Conversation
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
…ted 1 newline at end of file; 0 found
Tomcraft1980
approved these changes
Nov 13, 2025
Contributor
|
@modGTB Bitte mal approven. 😉 |
modGTB
approved these changes
Nov 13, 2025
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.
@Tomcraft1980 In Anlehnung zu PR #18 in dem die Checks von phpcs noch Fehlschlagen, kannst du erst diesen PR in main mergen. In diesem PR sind fast alle PSR12 Fehler behoben. Ich habe je Fehler-Beseitigung einen Commit in diesem PR gemacht. Ich denke so kann man es besser verstehen und nachvollziehen. Dir werden nach dem merge dann im PR #18 bei den Checks weniger Fehler angezeigt. Eigentlich habe ich nur ein PSR12 Coding Style WARNING übrig gelassen.