-
Notifications
You must be signed in to change notification settings - Fork 62
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
completion includes file extensions in import statements #1
Comments
I can implement it but we need consider it. For example, we need to remove only |
I am able to get file paths completed without the file extensions in compe. Initially I thought this was because of another source for dirs, but obviously that was when importing from a dir with an index file. What was really happening was that I got a result for the file from the lsp. I don't believe I got those results (file kind) from the lsp using the cmp plugin. Is there a difference with what results are shown from the lsp with compe vs cmp? This is no longer an issue with cmp-path, so you may close it. |
@pontus-albert Were you able to resolve this issue with extensions? I am having same problem |
I went back to compe. But I find my self wanting to create a custom source, so I will probably install cmp again, and tackle this issue again. Maybe the solution would be a separate source that does not include the file extension, so that you can choose what to complete, just like you could with compe. |
I'm getting the file path completion from typescript-language-server. |
Installed cmp again yesterday and it worked just like in compe. Don't know what went wrong the first time. The plugin is much improved in general since then too. Great work! Love how extendable it is. |
…te list' (hrsh7th#1) from folliehiyuki/cmp-async-path:fix-include-hidden into main Reviewed-on: https://codeberg.org/FelipeLema/cmp-async-path/pulls/1
Is it possible to exclude file extensions from the suggestions in the case of import statements in TypeScript?
The text was updated successfully, but these errors were encountered: