style: include PATH_TRAVERSAL_IN
#5148
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5148 +/- ##
============================================
+ Coverage 38.16% 38.26% +0.10%
Complexity 2362 2362
============================================
Files 517 516 -1
Lines 15350 15309 -41
Branches 2965 2958 -7
============================================
Hits 5858 5858
+ Misses 9205 9164 -41
Partials 287 287 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
vil02
force-pushed
the
include_PATH_TRAVERSAL_IN
branch
from
9605e4b to
ec66549
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes
TopKWords. This change will allow to include thePATH_TRAVERSAL_IN.I decided to remove the mentioned class because it was not tested and quite poorly implemented.
Continuation of #5144.
clang-format -i --style=file path/to/your/file.java