Closed Hoeksema closed 3 months ago
Issues
1 New issue
Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code
Hey @oformaniuk @StefH, hope you're having a great week! Any chance you could review this?
We're looking to keep our code base unforked from origin as much as possible, also so we can keep sending pull requests for issues we find as we productionize this in our system, and need this fix in particular for a critical use case of ours.
EDIT (Mar 7): Did not see any activity here, so we went ahead with forking unfortunately. No need to complete this soon anymore.
@Hoeksema, unfortunately, I was not following the repo closely lately. If you (and your team) is interested in contributing into the project further I'd be happy to include you as contributors.
Issues
1 New issue
0 Accepted issues
Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code
@Hoeksema, unfortunately, I was not following the repo closely lately. If you (and your team) is interested in contributing into the project further I'd be happy to include you as contributors.
Thank you for merging the PRs! Feel free to add me as contributor if that feels appropriate. We might need to make some more bug fixes in a quarter or two once we use it more broadly.
closes #566
The path parsing currently doesn't work properly when there are embedded slashes within an ignore block.
This PR fixes this issue:
//
within an escaped block/
to occur within an escape block without breakageBefore, the individual segments between slashes in addition to the entire escaped block were returned by PathInfo. Now, it returns just the latter, which is correct. All existing unit tests still pass and new tests were added to exercise the failing cases in #566.