Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bug with overriding options object #19

Merged
merged 1 commit into from
Apr 28, 2024

Conversation

addisonj
Copy link
Contributor

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 from connection.onInitialize, which seems like an error in understanding the API of the LSP library

This 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

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 from `connection.onInitialize`, which seems like an error
in understanding the API of the LSP library

This 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
@addisonj
Copy link
Contributor Author

For more context on this change, see markdoc/markdoc#500

@naourass
Copy link

Not sure if this is related, but the latest version is not working for me in vscode (I'm on wsl).

@filipproch
Copy link

filipproch commented Apr 28, 2024

No intent to spam but the extension (as is currently on the VSCode Marketplace) doesn't work at all (in sense of schema).
Can we expedite this fix? Its difficult to explain everyone to manually downgrade to 0.0.11 and avoid updates.
@segphault @mfix-stripe

Copy link
Contributor

@segphault segphault left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really sorry for the delay on this. Thanks for the fix!

@segphault segphault merged commit 4d43130 into markdoc:main Apr 28, 2024
2 checks passed
@segphault
Copy link
Contributor

I'll bump the version numbers and push a new release to the marketplace with this fix shortly

@louiss0
Copy link

louiss0 commented Jun 6, 2024

I'll bump the version numbers and push a new release to the marketplace with this fix shortly

It's not working for me now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants