Codecov Report

Merging #64 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #64      +/-   ##
============================================
+ Coverage     99.71%   99.73%   +0.02%     
- Complexity      138      146       +8     
============================================
  Files            10       10              
  Lines           347      377      +30     
============================================
+ Hits            346      376      +30     
  Misses            1        1

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 5bf53e7...0ad04de. Read the comment docs.

The last commit contains a test that is prop. best not merged to the repo, but is very handy when debugging.

Actually, I would keep it

The test in question interacts with the filesystem and assumes that patch is on the path. I think there is value in this as an integration test but it will of course not work on Windows, for instance.

of course it would not. that's why there is require OS
if the diff is suppose to be compatible with unified diff format, there is no better way to check it.

Sure; but even on Linux patch might not be available. I want this test, though :)

@SpacePossum , is there anything else in big epic of introducing line numbers ?

@keradus I've nothing major planned left for this.
At the moment I can see some refinements that can be made which I've listed in the description of the PR.
Like to hear what others think about the current state of the package and what features people are missing.
In terms of health, the repo has a near 100% test coverage, CS looks fair, performance and complexity looks good to me based on what the code does.

(thanks for reviewing/merging all btw. :) I'll clean up the test a bit more in the near future )

@SpacePossum Are we ready for the 2.0.0 tag?

And are any of those refinements BC breakers ?

since the API has been closed down as it is now (final on the classes) I think all ideas for refinements/additions can be done later without BC breakers.

@SpacePossum May I tag 2.0.0? Then the next step is to update PHPUnit etc. to the new API.

@sebastianbergmann lets do it :)
The changes on PHPUnit should be relative easy to do, lemme know if I can help out