-
Notifications
You must be signed in to change notification settings - Fork 206
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
[Spring Boot Tools] Flag to configure the "JAVA_HOME or PATH..." message display #478
Comments
@BoykoAlex Can you take a look at this (for the VSCode extension)? |
Yes. But... Unless it is hard/impossible to implement, I would prefer the error popup itself has a 'Do not show again' checkbox or something built in. If this popup is something that our language server launch code creates (rather than coming from vscode itself), then it shouldn't be too hard to implement that I think. This would be better than having the user need to realize all by themselves that they can disable the annoying popup by adding a setting somewhere manually. |
@BoykoAlex sounds good. |
Presumably there will still be a 'setting' to record that the popup is disabled. So you could set it 'in advance' if you really wanted to. I was just thinking that most users probably won't care to disable a popup unless they saw it at least once. And at that point if they were annoyed by the popup they might not even realize there exists an obscure setting that can disable it. |
That being said... I'm okay to go with the simpler solution of just having a setting with no extra widgetry in the popup. Avoid the extra work/complications of implementing this 'checkbox' in he UI if @offer8 who's requesting this feature doesn't really care about it anyway. |
Fixed with 08b1b4d @kdvolder I like the idea of having "Do not show again" button on that warning message. Don't think it complicated anything - a bit of investigation into VSCode API only :-) The setting is spring-boot.ls.checkJVM defaulted to |
Just one little nitpick. While I'm sure its technically almost the same whether a setting is 'true' or 'false' by default. However, my experience is that it tends to be a bit of a source of potential bugs when the default value is 'true' and you have to explicitly set it to 'false' to disable. The reason for this is some code may accidentally treat absence of a setting as being false instead of true. So, I've sort of come to the opinion/conclusion, that if possible, it is best to make newly added preferences so that their default value is actually false. So maybe we can switch this setting to be something like I don't feel too strongly about this, you can probably come up with good arguments to do the opposite (like some folks might thing it illogical to set something to 'true' to disable something :-) Anyhow @BoykoAlex, think about it and decide whether you agree. |
@kdvolder I'd keep it as is... other settings follow the same convention - off == |
Thanks for quick fix! |
Right, and if you want to try it early, you can download a snapshot .vsix file from the bottom of this page: |
I understand that the extension requires JDK in order for the live hover mechanism to work.
Assuming it is not a must can the following message:
be configured by a flag to prevent displaying it on extensions activation.
The text was updated successfully, but these errors were encountered: