-
Notifications
You must be signed in to change notification settings - Fork 144
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
reimplement deno.enablePatterns feature #153
Conversation
@turadg haven't seen it before |
@turadg Some more config checks are happening in https://github.com/denoland/vscode_deno/blob/master/typescript-deno-plugin/src/plugin.ts |
Thanks @lucacasonato . From a quick glance it looks like it'll be tricky to re-use this logic in the plugins module. Plus this method is doing a lot of unnecessary calculation repeatedly. Taking a step back, should "being enabled" be a concern of the extension itself? I think the problem is that Then defining the files for which it's enabled is handled by VS Code settings. E.g. to enable everywhere,
or to co-exist with other TS files,
|
I don't think we should add our own language ID. We don't change the syntax at all ( |
Deno has its own standard formatting which is different from other TypeScript formatters like Prettier.
What's a better way to determine whether a file is a Deno .ts file or a non-Deno .ts file?
What are the downsides of adding a language ID? I believe it could inherit from |
@axetroy what do you think? |
I didn't try this before. Add a new file type association |
Thanks for the PR, but we are doing a full extension rewrite so this will not be landed anymore. |
Attempting to add #92 after it was removed from master.
However, in my testing it's not working as expected. Even documents that don't match are getting Deno errors when
enabled
is true. For example,@Flaque did #92 have this problem?
This change is