This repository has been archived by the owner on Jul 16, 2019. It is now read-only.
normalize lsp line number, fix definition info for namespaced imports #86
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 fixes a bug that
vscode
refuses to go to definition of a namespaced import such as this based on information received from LSP server.The problem is that LSP server returns negative line number. This comes up because:
flow
returns a line number 0 fromget-def
in this casenuclide
's flow service (used by LSP server) decrements line number on this lineI am aware this could be treated as an upstream issue, but:
flow
has a test for this, so it seems that this behavior is by design.atom/nuclide
does not mind negative line number, so thenuclide
team might not be interested in this.Based on this, I concluded this is the best place to fix this.