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

New release required for getSupportedCodeFixes() to function correctly #18

Open
hoonoh opened this issue Nov 26, 2021 · 1 comment
Open

Comments

@hoonoh
Copy link

hoonoh commented Nov 26, 2021

Hi,

I had a struggle figuring out why getSupportedCodeFixes() was not working as expected so I tried using a build from most recent commit which functioned as expected.

It looks like 3af3ba3#diff-77817860eba34646cba9ba7ce0d125bafacc0163f65b18ee87caa2ebbeec82e1R201 is the main reason behind this.

@ivank
Copy link

ivank commented Jan 16, 2022

Struggling with similar thing myself - I can't seem to make getCodeFixesAtPosition to work at all, and wondered with its connected. Are there any docs about how the whole combo of getCodeFixesAtPosition / getSupportedCodeFixes / getSemanticDiagnostics is supposed to work together?

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

No branches or pull requests

2 participants