Use CFLint API directly, and use JSON configuration #33
Conversation
This file contains 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
|
It does also bump the version to 2.3.0 |
|
Thanks for that fix. I built from your repo using your patch and it fixed our build issue. Awesome! Hope your patch makes it into this repo soi that we can use the "official" build again. |
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.
This update uses the CFLint API directly rather than run through a command executor. This has the benefit of only scanning files matching the sonarqube inclusions/exclusions, rather than scan the entire codebase.
Also, use the JSON config format, as the XML format is deprecated.