-
Notifications
You must be signed in to change notification settings - Fork 111
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
LSP Umbrella #243
Comments
😬 I wasn't aware of this limitation. Is there a way around this somehow? Intellisense was a big part of why we wanted to support this. |
Please add displaying flow status to the list (current extension supports that feature). |
Features like rename symbol work through the LSP for TS, so if there's a way to track IDs through flows internals then it should be feasible |
Related issue in the |
Is this issue tracks usage with builtin extension disabled? |
You can create a separate issue for it. |
jsdoc support was implemented upstream. I just checked that box off |
We're going to track LSP (Language Server Protocol) related stuff, so we can reach feature parity with current extension.
@flow
(not sure if possible yet)relatedInformation
for richer diagnostics with Flow >=0.67 (PR LSP: make use ofrelatedInformation
for richer diagnostics #258).runOnEdit
runOnAllFiles
Nice to haves, but not sure if possible with
@builtin
TS disabled:@builtin
, there's no support for Rename Symbol, for instance./** foo */
). Maybe this should just be broken out from the main TS@builtin
so you can disable other TS features but keep the doc-block parsing feature? Otherwise I'm guessingflow-for-vscode
would have to reimplement this.cc @wbinnssmith @kpsroka @jslauthor @orta
The text was updated successfully, but these errors were encountered: