This way we open the door for further optimizations and make it possible to introduce customization of the output of the formatters per component-level.
Fixrangle/angular-devtools#171
The PR includes few changes:
1. Fixes a race condition between two competing async calls
2. Simplifies the message bus, now we have one method for getting the component tree instead of one for getting the component tree and another for getting properties. Similarly to GraphQL we send a query for exactly what we need.
3. Fixes the way we update properties in the UI once we receive new items
Currently, we only show which components are Angular elements. We don't visualize them in their position in the component tree, but only indicate with different coloring.
In the profiler we should also somehow show which tiles correspond to elements. We can discuss this further in rangle/angular-devtools#112.
* rangle/angular-devtools#13 - Highlight from the component tree to the application
* rangle/angular-devtools#13 - Highlight from the application to the component tree when using inspector
* Fixes on broken unit tests + added all files to coverage reports
* Setting test default to always generate coverage report
* rangle/angular-devtools#13 - Added basic test for component inspector
* feat(frontend): Moving component hover to tree to avoid passing messageBus rangle/angular-devtools#13
* feat(frontend): Sync hover from inspector to component tree rangle/angular-devtools#13
* feat(frontend): Rename function to retrieve ElementID from native element
* feat(frontend): Use separate handler to unhighlight from component instead of using highlight without ID
* feat(frontend): de-coupling inspector from the message bus
* feat(frontend): fix unit tests
