jens/flipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix image links with baseUrl

Browse Source 
Summary:
When using baseUrl in site config, it adds a prefix to all link paths.

But for assets, it doesn't work if you refer to them as `docs/assets/...`, you have to use just `assets/...`. Source: https://github.com/facebook/Docusaurus/issues/861

Reviewed By: passy

Differential Revision: D20796933

fbshipit-source-id: 2346e42b8b548f576a1e143f56ee5236eab55073
This commit is contained in:
John Knox
2020-04-02 03:12:06 -07:00
committed by Facebook GitHub Bot
parent cfb77148f7
commit 5ad8106e3f
20 changed files with 29 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/extending/client-plugin-lifecycle.md
View File

@@ -9,7 +9,7 @@ For both types of plugin, we recommend starting work after `onConnect` is called
## Regular Plugin Lifecycle
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.
![Regular Plugin Lifecycle diagram](/docs/assets/regular-plugin-lifecycle.png)
![Regular Plugin Lifecycle diagram](assets/regular-plugin-lifecycle.png)
## Background Plugin Lifecycle
For background plugins, `onConnect` is called when Flipper first connects, and `onDisconnect` when it disconnects. The user does not need to be viewing the plugin for it to send messages; they will be queued up until the next time the user opens the plugin where they will be processed.
@@ -19,5 +19,5 @@ Even for background plugins, `onDisconnect` and `onConnect` may be called on a p
Note that a plugin must be enabled by the user for its messages to be queued up.
</div>
![Background Plugin Lifecycle diagram](/docs/assets/bg-plugin-lifecycle.png)
![Background Plugin Lifecycle diagram](assets/bg-plugin-lifecycle.png)