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

Check one class per file & refactoring #79

Merged
merged 3 commits into from
Aug 5, 2016

Conversation

OndraM
Copy link
Member

@OndraM OndraM commented Aug 5, 2016

As per PSR-0 & PSR-4 there could only be 1 class in file. No other behavior was supported, however, if this rule wasn't followed, no exception nor warning was shown.

@OndraM OndraM added this to the 2.0 milestone Aug 5, 2016
@OndraM OndraM force-pushed the feature/one-class-per-file branch from cb9f8d0 to 414c0de Compare August 5, 2016 17:26
@OndraM OndraM force-pushed the feature/one-class-per-file branch from 414c0de to 9e9d749 Compare August 5, 2016 17:35
@coveralls
Copy link

coveralls commented Aug 5, 2016

Coverage Status

Coverage increased (+0.05%) to 74.218% when pulling 9e9d749 on OndraM:feature/one-class-per-file into 520b538 on lmc-eu:2.0.

@OndraM OndraM merged commit 051d050 into lmc-eu:2.0 Aug 5, 2016
@OndraM OndraM deleted the feature/one-class-per-file branch November 26, 2020 00:39
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