…es split pane gutter full height for profile details

…sualizer

)

… as a context object

…header when clicked (rangle/angular-devtools#714)

…te files

…iler

* docs: updating readme

* docs: updating readme

…ls#725)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…angular-devtools#731)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…me navigation (rangle/angular-devtools#716)

…to true

Previously the router parser uses private APIs to create the visualization for the router tree tab. Now the router parser always returns an empty router tree, effectively disabling the router tree tab until the necessary framework APIs are developed.

…ky tests

* feat: adding info popup

* Update projects/ng-devtools/src/lib/devtools-tabs/devtools-tabs.component.html

Co-authored-by: Minko Gechev <mgechev@gmail.com>

This PR intentionally ignores `Symbol`s because their serialization and deserialization will include extra complexity.

The changes also improve the typings in the continuation function that's passed during serialization.

…e/angular-devtools#753)

Previously, clicking the search icon on the component explorer did nothing. Now it focuses search input on click.

Previously if a component was inspected with the component inspector and that component was collapsed in the component explorer, the component would be selected but would not be viewable until the explorer was manually expanded.
Now ancestors are expanded on component inspection.

…g app found

Previously, Angular DevTools did not recognize the Angular application the second time the user reopens the extension tab. Webpack was preventing us to invoke twice a module with the same name. This PR changes the `content-script` to a library, allowing us to invoke it multiple times.

Rather than naively filter the flattened list, preserve the nesting by
filtering the original tree.

… production applications

The code was requesting index 0 of each item in the LView before checking
if it is an array. This causes issues with services that only allow calls to
properties that are defined on the service (backed by a strict ES6 proxy).
A check if the type is Array first corrects this issue.

fixes issue rangle/angular-devtools#802

Fix rangle/angular-devtools#798

…ols#733)

* ci: refactor circle config to use cypress orb

* ci: skipping unit tests while validating e2e runs

* ci: fix karma chrome launches

* ci: investigating karma headless failure

* ci: iterating on failure

* ci: move environment to executor

* build: revert karma config changes

* ci: update karma config

Co-authored-by: mgechev <mgechev@gmail.com>

…tools#812)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…devtools#808)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…angular-devtools#819)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…ls#810)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…angular-devtools#804)

* fix(backend): skip node if there is no associated TViewData

The code was assuming that the TViewData item at the same index as the node
in LView would contain a data entry. This value can be `null` (which is the
case in our app), which causes a catastrophic failure in the dev tool. By
checking for null, the node is skipped because it cannot determine the
associated component or directive and the dev tool does not die.

fixes issue rangle/angular-devtools#801

* chore: style tweak - add early return to avoid nesting

…ls#822)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…devtools#823)

Co-authored-by: Renovate Bot <bot@renovateapp.com>

…nge (rangle/angular-devtools#821)

Fix rangle/angular-devtools#786

With this PR now we consider not only the property name but also the
value of properties in the differ comparison.

The change also contains e2e and unit tests.