Fix analzyer support and add a test case #568
Merged
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
baronfel
force-pushed
the
analyzer-test-case
branch
from
b8d3562 to
3edb49c
Compare
…er for the warning
baronfel
force-pushed
the
analyzer-test-case
branch
from
3edb49c to
0373f04
Compare
…tionary, not the user-faceing filename
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 adds a test with a simple option analyzer (sample from the SDK) and verifies that we can in fact load and use analyzers.
The core problem was that on config changes, we need to ensure that we load analyzers from the configured paths, then they become available for use when we trigger the analyzer handling.