From c766dd535efc06e7a47f25e0e2306dd410370695 Mon Sep 17 00:00:00 2001 From: Wanja Tschuor Date: Wed, 11 Oct 2023 12:05:14 +0000 Subject: [PATCH] #10 fix incorrect onConfigUpdated event documentation --- docs/docs/core-api.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/docs/core-api.md b/docs/docs/core-api.md index 8f4ed9a..dcf2784 100644 --- a/docs/docs/core-api.md +++ b/docs/docs/core-api.md @@ -521,8 +521,7 @@ onUpdated(() => { }); ``` -The onUpdated hook is based on the `collage-context-updated` event, which is dispatched, everytime something on the own context changed. The event emits the updated context. -You can use the event if necessary, but you should prefere the hook. +The onConfigUpdated hook is also based on the `collage-context-updated` event, which is dispatched, everytime something on the own context changed. The event emits the updated context. You can use the event if necessary, but you should prefer the hook. ##### onConfigUpdated Executes a callback if the config of this context was updated. This hook takes a callback as first parameter. The second parameter is optional and represents the options argument of addEventListener.