Designer News
Where the design community meets.
almost 9 years ago from Bruno Daniel, Co-founder, Flying Dog
When you click on a Scope, the extension console.log()
s the DOM Node it's attached to. Clicking on a model console.log()
s the model value.
I understand this isn't obvious from the UI, and it's a usability issue that I'll address in an upcoming update.
Ahhh, I see! Yeah that isn't obvious, and would be cool if that information was shown in the UI itself.
Have you used Angular Batarang? It's really ugly and annoying to use, but allows you to expand and collapse the scope visually so you can narrow in on what you want. It also adds an Angular Properties panel to the specific element you inspect.
The ideal I think would be a mix of yours and Batarang's functionality.
I'm familiar with Batarang, it was the original inspiration. I wanted that functionality in browsers other than Chrome, while also addressing my own insatisfaction with its UI/UX.
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
It looks nicer than the competing extensions, but it doesn't seem to do much in terms of expanding/collapsing the scope or showing me the actual variables I want. Often they appear hidden in a level of the hierarchy I can't access. It shows there are a number of things in there, but clicking on it does nothing.
In fact everything you mouseover has a hover style, but nothing is actually clickable! Is mine buggy?