-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
No completion for "call" method on Function objects #39761
Comments
WIP (https://dart-review.googlesource.com/c/sdk/+/132920): Note that since |
Issue tracking IntelliJ cosmetics: https://youtrack.jetbrains.com/issue/WEB-43413. /fyi @DanTup in case you want to track this for VS Code. |
@pq thanks! I'll try it out and see how it looks. If I understand that issue correctly, the reason it doesn't appear the same is that IntelliJ is using its own data structures for this? In VS Code everything comes from the server, so if this shows up like any other method, I'd expect it to just work. I'll give it a test to confirm though! |
Thanks @DanTup. The issue is that ordinary method suggestions have a method element associated with them and that's how clients know it's a method invocation. These do not (since Feel free to ping me if you hit any snags. |
Could we do the special casing on the server side (by sending the information we would have sent had there been an element for it)? |
Ah, OK. @bwilkerson, yes. I was being thick. Looking at this again, I think we can. Will follow-up... |
@DanTup: please ignore, I've got a fix in flight on the server side. Everything should now "just work". Sorry for the noise! |
@pq np, and thanks! Is it https://dart-review.googlesource.com/c/sdk/+/133001? If so, is there anything special I need to do to see this? Using the most recent nightly ( |
Sweet! |
At the current version of dart sdk (2.7.0) we don't have a completion for the "call" method for function types. This is leading to third party sollutions to fix this problem, as of: simc/dartx#16 (comment)
The text was updated successfully, but these errors were encountered: