Enable automatic and interactive configuration of compile_commands.json path per project #26
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
Try to find it automatically in one of the parent directories, ask user for it, otherwise.
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.
Must not be merged before #25 (it includes these changes)
Instead of relying on a static property, lsp-sonarlint now mimics the behavior of SonarLint for VSCode and tries to find your compilation DB automatically in one of the parent directories for a given file.
If it fails to find it automatically, it will ask the user interactively and store the path for the workspace.
You can always change the selected path with
lsp-sonarlint-set-compile-commands.