Feature Request: Generated and Orphaned Routes | Controllers about ember-inspector

[teddyzeenny]

Identifying controllers that don't have routes is a bit tricky at the moment, especially in module based resolvers such as EAK. I plan on working a bit on the the container to support this kind of lookups, so maybe be can revisit this then.

As for identifying generated / defined controllers, you can do that by opening the Routes tab on page load and hovering over the controllers. Controllers that will be generated will not be clickable (inspectable).

[eccegordo]

OK thanks.
Makes sense about the module stuff obfuscating the important information. Still trying to better understand containers myself. Just out of curiosity, is this something that might be accomplished via inspection of the __container__.registry maybe that is a fruitful path?

Anyway closing this ticket for now. We can reopen in the future as feasibility increases.

[teddyzeenny]

The registry contains manually registered factories (container.register('store:main', App.Store)) which does not include controllers (except generated controllers and only after first lookup).