prevent display of "unexpected EOF" parser errors in diagnostics #2385
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.
Current Behavior:
The lsp server shows useless validation errors for empty graphql strings
Expected Behavior:
Ignore newlines and whitespace
Details:
the last release eliminated parse errors that would actually crash the server - these were my mistake, oops!
this fixes another annoying, non-useful parse error that is often seen when authoring a new operation
this should work in most cases, except for cases where there are only comments and no actual graphql types, but it's hard to come up with an efficient pass. this takes care of this bug, when authoring graphql and your cursor is here:
or with newlines:
or with whitespace & newlines:
or something as short as:
typ
where op validation doesn't need to kick in yet.