We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think the need of opening an openHAB related file can be confusing. Especially when one uses vscode mainly for openHAB configuration.
My idea is to start the extension on vscode startup, but provide a setting which prevents this behavior of one doesn't want it to be started directly.
Reference: https://code.visualstudio.com/api/references/activation-events#Start-up
The text was updated successfully, but these errors were encountered:
Maybe the better solution: https://code.visualstudio.com/api/references/activation-events#workspaceContains
Check for typical openhab folder structures and files and activate the extension immediately. No setting needed.
Sorry, something went wrong.
This would also be needed for the discussed jsr support in #141
Successfully merging a pull request may close this issue.
I think the need of opening an openHAB related file can be confusing.
Especially when one uses vscode mainly for openHAB configuration.
My idea is to start the extension on vscode startup, but provide a setting which prevents this behavior of one doesn't want it to be started directly.
Reference:
https://code.visualstudio.com/api/references/activation-events#Start-up
The text was updated successfully, but these errors were encountered: