Skip to content
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

Enhancement: Configure single_class_element_per_statement fixer to enforce single class element for const statements #587

Merged
merged 1 commit into from Mar 8, 2022

Conversation

localheinz
Copy link
Member

This pull request

  • configures the single_class_element_per_statement fixer to enforce single class element for const statements

💁‍♂️ For reference, see https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v3.7.0/doc%2Frules%2Fclass_notation%2Fsingle_class_element_per_statement.rst.

…force single class element for const statements
@codecov
Copy link

codecov bot commented Mar 8, 2022

Codecov Report

Merging #587 (02b5460) into main (7de9a2c) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##                main      #587   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity         7         7           
===========================================
  Files              2         2           
  Lines             20        20           
===========================================
  Hits              20        20           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7de9a2c...02b5460. Read the comment docs.

@localheinz localheinz force-pushed the feature/single-class-element-per-statement branch from 3aa514a to 02b5460 Compare March 8, 2022 22:00
@localheinz localheinz merged commit 1cf86d0 into main Mar 8, 2022
@localheinz localheinz deleted the feature/single-class-element-per-statement branch March 8, 2022 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants