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)

4
docs/extending/debugging.md
View File

@@ -17,13 +17,13 @@ As an alternative to using built-in Developer Tools you can also attach to the r
To attach the running Flipper instance open new tab in Google Chrome, navigate to "http://localhost:9222" and choose "Flipper" in the opened list.
![Attach From Google Chrome](/docs/assets/debugging-from-google-chrome.png)
![Attach From Google Chrome](assets/debugging-from-google-chrome.png)
## Visual Studio Code
If you prefer to use the same editor for both coding and debugging, you can attach to the running Flipper instance for debugging right from Visual Studio Code. First of all, you need to install extension "Debugger for Chrome". Then, to start debugging, open folder `desktop` of Flipper repository in VSCode, execute `yarn start` in terminal to launch Flipper in development mode, select tab `Debug and Run`, and run task `Attach to Running Renderer`. By default this task is set as the first one, so you can just press `F5` to run it.
![Attach From Visual Studio Code](/docs/assets/debugging-from-vscode.png)
![Attach From Visual Studio Code](assets/debugging-from-vscode.png)
## Plugin missing

2
docs/extending/layout-inspector.md
View File

@@ -6,7 +6,7 @@ title: Extending Layout Inspector
The Layout Inspector plugin can be extended to support new kinds of UI components. You can also extend it to customize the data made available in the sidebar.
Depending on whether you want to expose new data on Android or iOS, there are different interfaces you can use.
![Layout Inspector](/docs/assets/layoutinspector.png)
![Layout Inspector](assets/layoutinspector.png)
## Android