-
Notifications
You must be signed in to change notification settings - Fork 18
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
support trim specific extension on import #123
Comments
@mihai-vlc My use case is that in my project, vscode builtin typescript relative path module suggestion doesn't work. So I want to use this extension to support path suggestion. For now, we have setting I want to trim file extension for |
Hi @tjx666 , Can you try configuring the language specific settings in v1.23 ? "path-autocomplete.extensionOnImport": true,
"[typescript]": {
"path-autocomplete.extensionOnImport": false,
}, Please feel free to reopen the ticket if you still encounter issues. |
You may also want to combine this with |
I need use My thought is to let {
"path-autocomplete.extensionOnImport": {
"*.{ts,tsx,js,jsx}": false
}
} |
would something like this work ? "path-autocomplete.extensionOnImport": true,
"path-autocomplete.transformations": [
{
"type": "replace",
"parameters": [
"\\.\\w+$",
""
],
"when": {
"fileName": "\\.(ts|tsx|js|jsx)$"
}
}
], |
Nice work. |
In normal web project, when import
js/ts/jsx/tsx/mts/mjs/cjs
they needn't complete extension. But likeless/scss/png
etc need.So, it would be better to have a configuration to configure to make only trim specific extension on import.
@mihai-vlc
The text was updated successfully, but these errors were encountered: