Repository navigation
Use getter when determining whether custom config path is set in DetektGenerateConfigTask - #5157
Merged
Merged
Conversation
…ktGenerateConfigTask Fixes detekt#5097
BraisGabin
approved these changes
Jul 31, 2022
marschwar
approved these changes
Jul 31, 2022
cortinico
approved these changes
Jul 31, 2022
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #5097
Before this change, this task:
Would produce this output:
You can see the task was setting the config path and despite what was configured in the build file, the config wasn't being calculated correctly by the task.
With this PR, it will successfully generate the file:
And subsequent invocations will product the expected output: