-
Notifications
You must be signed in to change notification settings - Fork 36
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
"Open Inspector" never shows #7
Comments
Strange, it's showing it for me! Copied and pasted into a new file and it's working. |
is it to do with file name, e.g does the file have to follow a pattern such as |
Nope, no filename restriction! |
That's me all out of ideas on that one then 😅 |
It was figured out in Discord (yesterday, I think). You have to enable Code Lens for the prompt to appear over the machine definition. I just tested it and it works! The problem is, I don't like the clutter of Code Lens so this means I have to toggle it in settings before/after using the extension visualizer. |
it would be good to have a command to open the visualiser also I think @mattpocock for those who aren't a fan of the code lense? |
@damiensedgwick 100%! Could you add an issue? |
Certainly! |
It looks like we can close this issue - looks like a code lens thing. |
After installing the extension and visiting machine files, no "Open Inspector" link shows. I restarted VSCode for good measure. I even attempted different machines (I have quite a few).
I'm on MacOS Big Sur on an M1 architecture.
Here's an obfuscated version of the machine:
The text was updated successfully, but these errors were encountered: