From 83aee0cd7542a40d89800fd2c6afa73feeab83bb Mon Sep 17 00:00:00 2001 From: Pascal Hartig Date: Thu, 7 Mar 2019 02:59:10 -0800 Subject: [PATCH] Update create-plugin.md (#391) Summary: Remove a broken link and some outdated information Pull Request resolved: https://github.com/facebook/flipper/pull/391 Reviewed By: danielbuechele Differential Revision: D14342219 Pulled By: passy fbshipit-source-id: ab915618fe2ad3f955c465c091a636f9ea19ba33 --- docs/create-plugin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/create-plugin.md b/docs/create-plugin.md index 73a6f4764..8eef62291 100644 --- a/docs/create-plugin.md +++ b/docs/create-plugin.md @@ -148,4 +148,4 @@ void MyFlipperPlugin::didConnect(std::shared_ptr conn) { ## Background Plugins -If the plugin returns false in `runInBackground()`, then the Flipper app will only accept messages from the client side when the plugin is active (i.e. when user is using the plugin in the Flipper app). Whereas with the plugin marked as `runInBackground`, it can send messages even when the plugin is not in active use. The benefit is that the data can be processed in the background and notifications can be fired. It also reduces the number of rerenders and time taken to display the data when the plugin becomes active. As the data comes in the background, it is processed and a state is updated in the Redux store. When the plugin becomes active, the initial render will contain all the data. Currently, the network plugin is run in background. To setup the plugin in background, follow the above steps and for the JavaScript side follow the steps given [here](background-plugin-jsside.md). +If the plugin returns false in `runInBackground()`, then the Flipper app will only accept messages from the client side when the plugin is active (i.e. when user is using the plugin in the Flipper app). Whereas with the plugin marked as `runInBackground`, it can send messages even when the plugin is not in active use. The benefit is that the data can be processed in the background and notifications can be fired. It also reduces the number of rerenders and time taken to display the data when the plugin becomes active. As the data comes in the background, it is processed and a state is updated in the Redux store. When the plugin becomes active, the initial render will contain all the data.