From bd92bb7faf47df9da317711e75723541b4ab36e1 Mon Sep 17 00:00:00 2001 From: Kevin Strider Date: Thu, 24 Nov 2022 05:37:59 -0800 Subject: [PATCH] Creating Plugins Summary: This diff includes minor changes to the pages within the Creating Plugins section of Flipper Docs. Reviewed By: passy Differential Revision: D41497503 fbshipit-source-id: 5c5718b63bfff18322b28b547724415ab40a1810 --- docs/extending/client-plugin-lifecycle.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/extending/client-plugin-lifecycle.mdx b/docs/extending/client-plugin-lifecycle.mdx index 4cdee5285..2d9fe7b6f 100644 --- a/docs/extending/client-plugin-lifecycle.mdx +++ b/docs/extending/client-plugin-lifecycle.mdx @@ -13,7 +13,7 @@ For both types of plugin, it's recommended you start work after the `onConnect` For regular plugins, `onConnect` and `onDisconnect` are triggered when the user opens the plugin in the Flipper UI, and when they switch to another plugin, respectively. The process is illustrated in the following diagram. -Regular Plugin Lifecycle diagram +Regular Plugin Lifecycle diagram ## Background Plugin Lifecycle @@ -21,8 +21,8 @@ For background plugins, `onConnect` is called when Flipper first connects, and ` Even for background plugins, `onDisconnect` and `onConnect` may be called on a plugin (such as if the user restarts Flipper). Plugins should handle this accordingly by making sure to resend any important data to the reconnected instance. The process is illustrated in the following diagram. +Background Plugin Lifecycle diagram + :::warning Note that a plugin must be enabled by the user for its messages to be queued up. ::: - -Background Plugin Lifecycle diagram