Repository navigation
[ES6] Auto imports with completion #7849
Description
Activity
- addedSuggestionAn idea for TypeScriptAn idea for TypeScriptDomain: APIRelates to the public API for TypeScriptRelates to the public API for TypeScript
on Apr 6, 2016 Daniel Rosenwasser (@DanielRosenwasser) Mohamed Hegazy (@mhegazy) is there any chance that tsserver could provide this feature? If yes in which RoadMap? Thanks!
RyanCavanaugh commented
on Oct 26, 2016 MemberMore actionsThis would be really complex and is unlikely to be a priority relative to other work for quite a while
Thank's @RyanCavanaughfor your answer. I understand that it's not your priority but a lot of users from VSCode, typescript.java complains about this missing features compared to Jetbrains.
I know that there are VSCode extension to do that, but it's not clean because there are double TypeScript parsing (one by tsserver and one by the extension). It should be very cool if tsserver provides this feature.
#11768 would handle part of that, though not through completion but through quick fixes.
Thanks Mohamed Hegazy (@mhegazy) for your answer. #11768 is a great feature. I'm implementing quickfix support inside Eclipse. I'm very enthousiasm to test it once my implementation will be finished.
Do you think you could use #11768 logic to support auto import with completion?
Do you think you could use #11768 logic to support auto import with completion?
What i meant is the user would get some of the functionality with the quick fix. possibly we can leverage some of the logic later on to support the feature in the OP.
the main issue is that we need to have our completion include some sort of edit ranges, so that accepting the completion would generate multiple changes in the file. which is not that hard to do to be frank, bit it is work.
Thanks again Mohamed Hegazy (@mhegazy) to have taking time to answer me.
What i meant is the user would get some of the functionality with the quick fix.
Yes it's already a great improvement.
possibly we can leverage some of the logic later on to support the feature in the OP.
It was the answer that I wished:) Hope one day auto import will be implemented.
the main issue is that we need to have our completion include some sort of edit ranges, so that accepting the completion would generate multiple changes in the file. which is not that hard to do to be frank, bit it is work.
Ok I understand. I though the hard task was about the scan files (to have the best performance), because in this case you must scan about the whole ts files in the project and not only declared files as module (with import, require).
- addedVS Code TrackedThere is a VS Code equivalent to this issueThere is a VS Code equivalent to this issue
on Nov 2, 2016 Feedback from VS Code users - microsoft/vscode#818
Mohamed Hegazy (@mhegazy) I'm sorry to insist with this feature, but is there an chance that auto import could be added inside RoadMap https://github.com/Microsoft/TypeScript/wiki/Roadmap ?
Reacted by Jake Brownson, Donald Pipowitch, prog110 and hakonamatataWe are planning the next release now. should have more information about what we can take on soon.
Reacted by Donald Pipowitch and Anthony CiccarelloThank's Mohamed Hegazy (@mhegazy)!
This more than anything else is the biggest hurdle for users to move away from Webstorm.
Note sure why it is not yet listed in the Roadmap as of yet :(Reacted by Jake Brownson, Arlair and Charl43 remaining items
- assigned and unassigned
on Aug 21, 2017 - addedFixedA PR has been merged for this issueA PR has been merged for this issue
on Oct 16, 2017 Fixed by #19069
Reacted by Akshar Patel, Alexander Peters, Zsolt Paral, Alfonso Andrés López Molina, Naor Ami and Marius SchulzReacted by Marco Buono and Naor Ami- locked and limited conversation to collaborators
on Jun 19, 2018
It should really fantastic if tsserver completion command could support auto import with completion like WebStorm provides:
See http://blog.jetbrains.com/webstorm/2016/04/angular-2-workflow-in-webstorm/#ng2-imports for more information.