Angular state inspector에 대한 리뷰
Angular state inspector 제작자: Ihor Klymenok
Ihor Klymenok 님의 답글
개발자 답글
5년 전에 게시됨Thank you for your feedback.
All issues were fixed and now extension should work like a charm :)
But if you still occurred with a problem, please contact with me by email with more descriptive response how your problem looks like.
All issues were fixed and now extension should work like a charm :)
But if you still occurred with a problem, please contact with me by email with more descriptive response how your problem looks like.
리뷰 12개
- 5점 만점에 4점Noitcereon 님, 3년 전Does what it says. You can inspect the state in the Inspector tool on a locally running Angular project. It is not as convenient as other dev tools such as for Vue or React.
- First of all, I'm very thankful this exists. Now that augury in firefox is broken, this is my only way to effectively debug in angular on that browser. it is functional and I like it.
However, it does seem like sometimes the application's interface sort of breaks. At least it does for my custom components.개발자 답글
4년 전에 게시됨Thank you for the feedback.
Starting from version 1.5.0 "broken interface" issue should be fixed. - 5점 만점에 5점Carlos Barros 님, 5년 전
- Kinda difficult to use because the "State" tab is located at the very end of the inspector panel, which means it definitely takes a lot more space than it needs,
not necessarily your fault, firefox is the one to blame here.
But I guess you could create a new major tab (along with "inspector", "debugger", "network", etc.) which contains the whole virtual dom tree, this way you can skip the native HTML elements which don't have angular state too! (although you can consider to add those as properties shown like `template` or `child` etc) 개발자 답글
5년 전에 게시됨Thank you for your feedback.
More information and screenshots were added to the description area so you can read a little bit more about how to work with it.- 5점 만점에 4점Firefox 사용자 14765376 님, 6년 전
- 5점 만점에 5점Firefox 사용자 15036059 님, 6년 전
개발자 답글
5년 전에 게시됨Thank you for your feedback.
All issues were fixed and now extension should work like a charm :)
But if you still occurred with a problem, please contact with me by email with more descriptive response how your problem looks like.- 5점 만점에 5점Firefox 사용자 14699223 님, 6년 전