Fix bug with overriding options object #19
Merged
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.
Recently, with the addition of supporting running LSP as a standalone process, the
connect
function was changed.This changed the promise such that the options object was now the result of the
connection.onInitialized
function rather than the result of the callback fromconnection.onInitialize
, which seems like an error in understanding the API of the LSP libraryThis reverts that change, but still returns the value options out of the promise, though it is likely an uneeded change.
Automated testing for this would be ideal, but as there doesn't seem to be any infrastructure for that currently, that is out of scope of this commit