doc: complete & improve webhook doc

MAIF · Jun 16, 2024 · f635dde · f635dde
1 parent 7fb18da
commit f635dde
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 9 deletions.
diff --git a/izanami-frontend/tests/screenshots/index.ts b/izanami-frontend/tests/screenshots/index.ts
@@ -12,7 +12,7 @@ import { generate as userInvitationGenerate } from "./user-invitation";
 import { generate as webhookGenerate } from "./webhooks";
 
 async function generateAll() {
-  /*await apiKeyGenerate();
+  await apiKeyGenerate();
   await bulkGenerate();
   await contextGenerate();
   await gettingStarted();
@@ -21,7 +21,7 @@ async function generateAll() {
   await multiConditionFeatureGenerate();
   await queryBuilderGenerate();
   await userInvitationGenerate();
-  await base64Wasm();*/
+  await base64Wasm();
   await remoteWasmoGenerate();
   await webhookGenerate();
 }

diff --git a/manual/docs/04-guides/12-webhooks.mdx b/manual/docs/04-guides/12-webhooks.mdx
@@ -52,13 +52,14 @@ It's useful to make sure that your template work as expected.
 
 ## Webhook call
 
-Webhook is called :
-
-- When feature is created under given scope
-- When feature concerned by given scope is deleted
-- When enabling of feature concerned by given scope is modified
-- When activation conditions of feature concerned by given scope are modified
-- When an overload is created / updated / deleted for a feature concerned by given scope
+Webhook is called for a feature in scope when:
+
+- it's created
+- it's deleted
+- its enabling is modified
+- its activation conditions are modified
+- an overload is created / updated / deleted for it
+- its name changes (we need to call webhook since user based activation condition rely on name)
 
 ## Resilience