feat(core): introduce debugName optional arg to framework signal functions #57073
Conversation
6d94bb9 to
ef5240b
Compare
There was a problem hiding this comment.
Thanks @AleksanderBodurri, this look great! A lot more places to update than I expected. 😅
I just have one question about ngDevMode usage and a few minor nits, but nothing too significant here.
| @@ -56,7 +61,7 @@ export interface ModelSignal<T> extends WritableSignal<T>, InputSignal<T>, Outpu | |||
| * Can be set to {@link REQUIRED_UNSET_VALUE} for required model signals. | |||
| * @param options Additional options for the model. | |||
| */ | |||
| export function createModelSignal<T>(initialValue: T): ModelSignal<T> { | |||
| export function createModelSignal<T>(initialValue: T, opts?: ModelOptions): ModelSignal<T> { | |||
There was a problem hiding this comment.
ModelOptions's alias isn't used in the function. Should we narrow down the type here ?
70c8e84 to
8ce5039
Compare
| @@ -34,5 +39,8 @@ export function computed<T>(computation: () => T, options?: CreateComputedOption | |||
| if (ngDevMode) { | |||
| getter.toString = () => `[Computed: ${getter()}]`; | |||
| } | |||
|
|
|||
| getter[SIGNAL].debugName = options?.debugName; | |||
There was a problem hiding this comment.
Should we not assign this only inngDevMode above? Also, we should conditionally assign only if options?.debugName is defined (otherwise we add an extra property to all nodes of this type, which has a high memory cost).
e96e1f7 to
3d7835b
Compare
53a0a0a to
a15259f
Compare
…tions Angular DevTools is working on developing signal debugging support. This commit is a step in the direction of making available debug information to the framework that will allow Angular DevTools to provide users with more accurate information regarding the usage of signals in their applications. Follow up PRs that will use this arg will: - Develop a typescript transform that will detect usages of signal functions and attempt to add a debugName without the user needing to specify one directly - Develop debug APIs for discovering signal graphs within Angular applications (using debugName as a way to label nodes on the graph)
a15259f to
48b42ee
Compare
|
I see that you just added the If you want your PR to be merged, it has to pass all the CI checks. If you can't get the PR to a green state due to flakes or broken |
|
Caretaker: this is "green" in g3. |
|
This PR was merged into the repository by commit ec386e7. The changes were merged into the following branches: main |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Blocked by #57710
Angular DevTools is working on developing signal debugging support. This commit is a step in the direction of making available debug information to the framework that will allow Angular DevTools to provide users with more accurate information regarding the usage of signals in their applications.
Follow up PRs that will use this arg will: