-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Differentiate between vue inspector
and component tree inspector
#294
Comments
Do you mean the |
I mean the main target button next to the vue icon at the bottom (you can also see it when the devtools is minimized), it act like the Thank you for the doc. I installed the
|
Agree with that, PR welcome. |
It can be an "edit" pen.
This one may be a bit too simplistic. If you have a specific icon I can make a PR. |
You can choose one from Commonly it will be |
In the overlay package there's no unocss package installed and the target icon is the svg that I edited and pasted in my previous comment. I can copy an icon from iconify to replace the current svg. |
Oh, then |
I made a PR with the this icon, I can use another one if there's better. |
vue inspector
and component tree inspector
I just updated all my vue/vite dependencies and installed vue-devtools 7.0.21. I'm on macOS Sonoma 14.4.
When I use the target button inside the components tab, the devtools is minimized, I can select a component on my website and it will open in the devtools. Everything works very well.
When I do the same with the main target button next to the vue icon, the devtools is not minimized, it doesn't do anything in the devtools and open the file with a broken vim in vscode (I can't use vim commands, whatever I do will insert some characters). Basically it does the same as the "open in editor" button does.
Also if I click again on the target it doesn't stop the component selection so it doesn't seem like it's a toggle like its title suggest.
Shouldn't the 2 target button have the same behavior (especially the fact that the devtool is hidden to select the component)?
When the component is opened in the editor is it possible to open the file directly in vscode instead of creating a vim session in the current terminal?
The text was updated successfully, but these errors were encountered: