Why does envkey-vscode display information in the Problems panel? #72
-
I'm curious about the decision to display context information about EnvKey variables in the Problems panel when using the VSCode extension. Is this the only way to provide this information to the hover/peek window when hovering over a symbol in the editor? This makes sense for those variables declared in the code, but EnvKey can't find a value for them ( I realize it's a small thing aesthetically, but it's been getting in the way of my cognitive flow when reviewing or refactoring code to the point that I'm not sure if there's much benefit to using it. Is this by design? What's the logic behind doing it this way? Will it change at some point in the future? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
There unfortunately doesn't seem to be a way to add VSCode diagnostics, which provide the underlining/hover behavior, without also having them show in the Problems panel. I agree it's annoying and would be happy to change it if VSCode offers an alternative in the future. |
Beta Was this translation helpful? Give feedback.
There unfortunately doesn't seem to be a way to add VSCode diagnostics, which provide the underlining/hover behavior, without also having them show in the Problems panel. I agree it's annoying and would be happy to change it if VSCode offers an alternative in the future.