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: Require phpstan/phpstan-deprecation-rules #156

Merged
merged 3 commits into from Jan 8, 2019

Conversation

localheinz
Copy link
Member

@localheinz localheinz commented Jan 7, 2019

This PR

  • requires phpstan/phpstan-deprecation-rules
  • includes rules.neon from phpstan/phpstan-deprecation-rules
  • ignores an error involving a deprecated test method

@localheinz localheinz self-assigned this Jan 7, 2019
@codecov
Copy link

codecov bot commented Jan 7, 2019

Codecov Report

Merging #156 into 1.x will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##                1.x     #156   +/-   ##
=========================================
  Coverage     82.77%   82.77%           
  Complexity       36       36           
=========================================
  Files             2        2           
  Lines           180      180           
=========================================
  Hits            149      149           
  Misses           31       31

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 13c76b9...0f59f6c. Read the comment docs.

@localheinz localheinz force-pushed the feature/phpstan-deprecation-rules branch from 431dc99 to 77f73e8 Compare January 8, 2019 07:35
@localheinz localheinz merged commit a848059 into 1.x Jan 8, 2019
@localheinz localheinz deleted the feature/phpstan-deprecation-rules branch January 8, 2019 11:38
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

1 participant