You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/content/docs/challenges/signal/53-big-signal-performance.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@ description: Challenge 53 is about performance while using big signal object
4
4
author: thomas-laforge
5
5
contributors:
6
6
- tomalaforge
7
+
- jdegand
7
8
challengeNumber: 53
8
9
command: signal-big-signal-performance
9
10
sidebar:
@@ -13,11 +14,12 @@ sidebar:
13
14
14
15
## Information
15
16
16
-
In this challenge, you can imagine a big application where you store your user state inside a service and you use this service to use your user anywhere in your application.
17
-
The issue is when you update one property of your user, the entire application is updating.
17
+
For this challenge, you can imagine a large-scale application where you use a service to save and retrieve your user state at any time within the application.
18
18
19
-
I added the `CDFlashingDirective` to vizualise when one component is rerendering.
19
+
The problem is that updating a single user property updates the entire application.
20
+
21
+
I added the `CDFlashingDirective` to visualize when one component is rendering.
20
22
21
23
## Statement
22
24
23
-
With Signal, you can now be more fine-grained in what the UI is rerendering. The goal of this challenge is to understand why everything is rerendering and you refactor the application to be more performante.
25
+
With signals, you can now be more fine-grained in what the UI is rendering. The goal of this challenge is to understand why everything is re-rendering and to refactor the application to be more performant.
0 commit comments