-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Display a signal graph for each component #60478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
...s/ng-devtools/src/lib/devtools-tabs/directive-explorer/signals-view/signals-tab.component.ts
Outdated
Show resolved
Hide resolved
f54c855
to
990a546
Compare
fceca82
to
aac9d26
Compare
c21e2b5
to
7601a56
Compare
e50fd0d
to
78472e1
Compare
95f6448
to
97d9d59
Compare
a8f616b
to
bf422af
Compare
@milomg, is this PR still relevant? |
@hawkgs this PR is basically the end UI goal for the signals view, and has a few features that likely will not be part of the initial MVP, such as logging and a button to open the signals graph from the property view (in addition to the button to open the signals graph from the directive explorer). Each of the 9 signal graph PRs were just commits of this mega PR, so this is how I've been testing each of the PRs together |
f86b3c6
to
13e176b
Compare
Use responsive-split for the signal graph tab.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
(note the dashed line here is animated in the direction of the consumer)
Does this PR introduce a breaking change?
Other information