You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered an issue where this extension behaves differently between local and Remote-WSL development environments.
For some languages such as Java, JavaScript, TypeScript, CSS, and HTML, Better Comments work as expected both on local and Remote-WSL. However, for certain languages like Solidity, Better Comments work as expected on local development but do not apply in the Remote-WSL environment.
I found this comment : #344 (comment) @aaron-bond Here you say that you found a way to enable it to work for all languages, as long as user has language extension that tells Better Comments about the format.
My guess why it is behaving different for some languages is:
you provided manual guidance for some of them like Java, JS, TS, etc... This is why they work on both local and remote
for those languages that you didn't strictly specify, they work only on local
My question for @aaron-bond is : Is there a way to apply this automatic check on remote development too?
If there is no way to enable it automatically, I would like to manually specify some languages like Solidity but I will need some guidance on how to do so. If you can provide guidance on how to add different languages manually, I believe that this issue would be fixed and people would be able to create pull request for languages that they want to use this extension for.
The text was updated successfully, but these errors were encountered:
I've encountered an issue where this extension behaves differently between local and Remote-WSL development environments.
For some languages such as Java, JavaScript, TypeScript, CSS, and HTML, Better Comments work as expected both on local and Remote-WSL. However, for certain languages like Solidity, Better Comments work as expected on local development but do not apply in the Remote-WSL environment.
I found this comment : #344 (comment)
@aaron-bond Here you say that you found a way to enable it to work for all languages, as long as user has language extension that tells Better Comments about the format.
My guess why it is behaving different for some languages is:
My question for @aaron-bond is : Is there a way to apply this automatic check on remote development too?
If there is no way to enable it automatically, I would like to manually specify some languages like Solidity but I will need some guidance on how to do so. If you can provide guidance on how to add different languages manually, I believe that this issue would be fixed and people would be able to create pull request for languages that they want to use this extension for.
The text was updated successfully, but these errors were encountered: