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

fix(InteractiveIgnorer): use FilePath #1624

Closed
wants to merge 2 commits into from

Conversation

eliblock
Copy link
Contributor

@eliblock eliblock commented Jul 20, 2021

Fixes #1622.

The refactor of ignore files to use FilePath in #1620 did not include
the InteractiveIgnorer. Complete the refactor.

The original PR included the refactor to FilePath in order to update
ignorefile pathing to match other pathing within Brakeman, which in turn
permitted the SARIF report to use the pre-loaded relative path in its
output.

As noted in #1622, this had the unintended side effect of making the
path of -i configurations relative to the app root (if an absolute
path was not provided), rather than relative to where the command was
run. This differs from the behavior of the -c flag, may be
undesired, and is not addressed in this PR.

@eliblock
Copy link
Contributor Author

#1623 reverted the cause of the issue.

@eliblock eliblock closed this Jul 20, 2021
Repository owner locked and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Interactive ignore tries to call empty? on a Brakeman::FilePath and fails
1 participant