From 61fd4183fc0430419e7e63ffb6bbb1dade7b7a5b Mon Sep 17 00:00:00 2001 From: thomas Date: Wed, 22 May 2024 09:11:28 +0200 Subject: [PATCH] feat: add new constraint to latest challenge --- .../content/docs/challenges/signal/51-function-call-effect.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/src/content/docs/challenges/signal/51-function-call-effect.md b/docs/src/content/docs/challenges/signal/51-function-call-effect.md index 91d02bd..9a25314 100644 --- a/docs/src/content/docs/challenges/signal/51-function-call-effect.md +++ b/docs/src/content/docs/challenges/signal/51-function-call-effect.md @@ -20,3 +20,7 @@ In this second challenge focusing on Signal effects, we've introduced an input s Ideally, the system should log an action only when one is specifically selected. However, we currently face an issue where changing the user also triggers a log entry, even though we do not explicitly monitor user changes. The objective of this challenge is to identify and resolve the cause of these extra triggers. We aim to ensure that logging only occurs when an action is selected. + +## Constraints + +- You cannot modify the `UserService` file.