search

rangle / augury

Angular Debugging and Visualization Tools
https://augury.rangle.io
MIT License
2.01k stars 216 forks source link

Unable to view entryComponents, modals, etc. #1380

Open andrewthauer opened 5 years ago

andrewthauer commented 5 years ago

Consolidating a various issues related to the inability to view/debug entryComponents (e.g. dialogs).

xyrintech commented 5 years ago

Any update for this?

alexander-kastil commented 5 years ago

Augury is such a great tool ... it‘s a pitty that it does not work on material dialogs

wbeeftink commented 5 years ago

Would love to have this feature.

furkee commented 5 years ago

Still no updates? This would be a great feature.

jurkov commented 4 years ago

Do you know any workaround?

jurkov commented 4 years ago

https://github.com/rangle/augury/blob/82df66e94f94d0aafb617e09d0eb8c76437de600/src/backend/backend.ts#L208

A dirty workaround to see mat-dialog-0 is to modify augury with the following snippet:

getAllAngularRootElements() .map(root => ng.probe(document.getElementById('mat-dialog-0'))) .filter(debugRoot => debugRoot !== null);

benwinding commented 4 years ago

https://github.com/rangle/augury/blob/82df66e94f94d0aafb617e09d0eb8c76437de600/src/backend/backend.ts#L208

A dirty workaround to see mat-dialog-0 is to modify augury with the following snippet:

getAllAngularRootElements() 
.map(root => ng.probe(document.getElementById('mat-dialog-0'))) 
.filter(debugRoot => debugRoot !== null);

Can this be implemented into a PR? Would love to see this fixed in Augury

dawsnap commented 4 years ago

+1 This issue affects me using a component inside a ng-bootstrap modal

renaem commented 3 years ago

+1