docs: clarify plugins don't update devtools timeline (#1002)

Co-authored-by: Eduardo San Martin Morote <posva@users.noreply.github.com>

diff --git a/packages/docs/core-concepts/plugins.md b/packages/docs/core-concepts/plugins.md
index 9319d5ee88ed4aaa23265b3861b92f5e9eaf8fe3..25d89622efb73bc5ecc2f4e1b6d5e51ca5f262b6 100644 (file)
--- a/packages/docs/core-concepts/plugins.md
+++ b/packages/docs/core-concepts/plugins.md
@@ -131,6 +131,8 @@ pinia.use(({ store }) => {
 })
 ```
 
+Note that state changes or additions that occur within a plugin (that includes calling `store.$patch()`) happen before the store is active and therefore **do not trigger any subscriptions**.
+
 :::warning
 If you are using **Vue 2**, Pinia is subject to the [same reactivity caveats](https://vuejs.org/v2/guide/reactivity.html#Change-Detection-Caveats) as Vue. You will need to use `set` from `@vue/composition-api` when creating new state properties like `secret` and `hasError`: