fix(hover): skip unsupported hover nodes#754
Merged
Merged
Conversation
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
1 participant
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.
Avoid crashing hover requests when the cursor is on a parsed node that the hover engine recognizes but does not yet implement, such as policy names in
DROP POLICYstatements. Unsupported hover targets now return no hover result instead of panicking, and empty hover results propagate asNonethrough the LSP handler.Regression Coverage
Adds a regression test for hovering over a quoted policy name in
DROP POLICY IF EXISTS, matching the crash reported in the issue.Fixes #753