"State" section of Properties window doesn't always show up.

[xouqoa]

Augury version (required): 1.7
Angular version (required): 4.1.1
Date: 5/16/2017
OS: Windows 10

This is more of a general question than an actual issue, perhaps.

Some of our components don't show the State section of the properties window. It worked in the past, and then at some point it stopped. I'm not sure if this is a code change thing, or an actual issue with Augury.

I guess what I'm trying to find out is if there are any common code pitfalls that can cause this issue or not. In one parent component, we have a child component that doesn't show anything, and a separate child component that functions as expected. It's kinda weird and I'm just not sure what to look for/at.

[JanEggers]

same issue here,

it would be nice that in case augury is not able to display the state to generate a logmessage in the console or in the area the state would normally show up. that way we could provide better feedback whats not working or fix the issue in that component

[colthreepv]

I am having the same issue with version 1.9
Are you sure your version is 1.7? Chrome extensions should auto-update

[xouqoa]

I uninstalled/installed to get 1.9 -- it wasn't doing it automatically (Chrome Canary). Problem seems to be resolved for me at least. I'll keep an eye on it.

[xouqoa]

Still having issues with the State section not showing up. Would this have anything to do with lazy loaded modules, maybe?

Also, with the 1.9 update, I have to close the F12 tools if I reload my page or I get the "this is not an angular application" message in Augury. Separate issue I'm sure, but figured I'd mention it.

[AlrikOlson]

I noticed when we had a property that contained a "." in the name that the State section stopped showing up. As soon as we replaced the "." in the property, the State section showed up again.

This does not work:
var options = { ... ... events: { 'froala.editor': true } }

This does work:
var options = { ... ... events: { 'froalaeditor': true } }

[mhengelein]

Still having this issue with 1.15.0. :(

[jacobedawson]

I'm having this issue with 1.15.0 / Angular 5- not having the state available greatly reduces the use cases for this extension...

[jainvishal520]

Any updates on this? I'm not able to see component states!

[sunstar007]

Same here - I don't see the state on many of the components in our Angular 5 application (works on some components though). There's no error message to indicate what could be wrong, and the components are very similar in the way they're structured

[kpodkalicki]

Same here - no state of components visible for Angular 5 app.