Skip to content

[TASK] Add more PHP-CS-Fixer rules #631

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

Merged
merged 1 commit into from
Jul 3, 2024
Merged

[TASK] Add more PHP-CS-Fixer rules #631

merged 1 commit into from
Jul 3, 2024

Conversation

oliverklee
Copy link
Collaborator

@oliverklee oliverklee commented Jul 1, 2024

Also drop some rules that are already in included in the used
rulesets.

@oliverklee oliverklee requested a review from sabberworm July 1, 2024 10:24
@oliverklee oliverklee self-assigned this Jul 1, 2024
@oliverklee oliverklee marked this pull request as draft July 1, 2024 10:24
@oliverklee oliverklee force-pushed the task/more-fixer-rules branch 5 times, most recently from a74eb08 to be7de5d Compare July 3, 2024 16:42
@oliverklee oliverklee changed the title [TASK] Add more PHP-CS-Fixer rules and autoformat the code [TASK] Add more PHP-CS-Fixer rules Jul 3, 2024
@oliverklee oliverklee removed the request for review from sabberworm July 3, 2024 16:42
@oliverklee oliverklee force-pushed the task/more-fixer-rules branch from be7de5d to 4528686 Compare July 3, 2024 16:44
@oliverklee oliverklee requested review from JakeQZ and sabberworm July 3, 2024 16:44
@oliverklee oliverklee marked this pull request as ready for review July 3, 2024 16:44
@oliverklee
Copy link
Collaborator Author

Note: I'll need to add some type casts (in separate PRs) before we can make all files strict.

Also drop some rules that are already in included in the used
rulesets.
@oliverklee oliverklee force-pushed the task/more-fixer-rules branch from 4528686 to 78361d0 Compare July 3, 2024 16:46
Copy link
Collaborator

@JakeQZ JakeQZ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also drop some rules that are already in included in the used rulesets.

Actually, the rules being removed have the value being set as the default. So I'm wondering if they should be kept, to be explicit, or removed anyway, to avoid clutter.

Otherwise, this brings the config in line with the Emogrifier project, so we have consistency.

@oliverklee
Copy link
Collaborator Author

Actually, the rules being removed have the value being set as the default. So I'm wondering if they should be kept, to be explicit, or removed anyway, to avoid clutter.

I don’t care much either way - as long as the config file is consistent between our two projects. :-)

Copy link
Collaborator

@JakeQZ JakeQZ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t care much either way - as long as the config file is consistent between our two projects. :-)

Neither do I, TBH. It was just an observation. Emogrifier doesn't have them, so for consistency we may as well remove them here.

@JakeQZ JakeQZ merged commit fdcf59d into main Jul 3, 2024
18 checks passed
@JakeQZ JakeQZ deleted the task/more-fixer-rules branch July 3, 2024 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants