Skip to content

Commit

Permalink
Fix lint rules in version 0.61 (facebook#1339)
Browse files Browse the repository at this point in the history
* Fix lint rules in version 0.61

* Fix lint rules in version 0.61

* Update website/versioned_docs/version-0.61/debugging.md

Co-Authored-By: Ricky <[email protected]>
  • Loading branch information
bolah2009 and rickhanlonii committed Oct 14, 2019
1 parent 0c9962b commit e83564c
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
1 change: 0 additions & 1 deletion .alexignore
Original file line number Diff line number Diff line change
Expand Up @@ -66,4 +66,3 @@ website/versioned_docs/version-0.57/
website/versioned_docs/version-0.58/
website/versioned_docs/version-0.59/
website/versioned_docs/version-0.60/
website/versioned_docs/version-0.61/
3 changes: 2 additions & 1 deletion website/versioned_docs/version-0.61/debugging.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ Open the in-app developer menu and choose "Toggle Inspector". It will bring up a

![React Native Inspector](/react-native/docs/assets/Inspector.gif)

However, when `react-devtools` is running, Inspector will enter a special collapsed mode, and instead use the DevTools as primary UI. In this mode, clicking on something in the simulator will bring up the relevant components in the DevTools:
However, when `react-devtools` is running, Inspector will enter a collapsed mode, and instead use the DevTools as primary UI. In this mode, clicking on something in the simulator will bring up the relevant components in the DevTools:

![React DevTools Inspector Integration](/react-native/docs/assets/ReactDevToolsInspector.gif)

Expand Down Expand Up @@ -160,6 +160,7 @@ On Android 5.0+ devices connected via USB, you can use the [`adb` command line t

`adb reverse tcp:8081 tcp:8081`

<!-- alex ignore host-hostess -->
Alternatively, select "Dev Settings" from the Developer Menu, then update the "Debug server host for device" setting to match the IP address of your computer.

> If you run into any issues, it may be possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. Try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.
Expand Down
2 changes: 1 addition & 1 deletion website/versioned_docs/version-0.61/fast-refresh.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Fast Refresh is a React Native feature that allows you to get near-instant feedb

## How It Works

- If you edit a module that **only exports React component(s)**, Fast Refresh will update the code just for that module, and re-render your component. You can edit anything in that file, including styles, rendering logic, event handlers, or effects.
- If you edit a module that **only exports React component(s)**, Fast Refresh will update the code only for that module, and re-render your component. You can edit anything in that file, including styles, rendering logic, event handlers, or effects.
- If you edit a module with exports that _aren't_ React components, Fast Refresh will re-run both that module, and the other modules importing it. So if both `Button.js` and `Modal.js` import `Theme.js`, editing `Theme.js` will update both components.
- Finally, if you **edit a file** that's **imported by modules outside of the React tree**, Fast Refresh **will fall back to doing a full reload**. You might have a file which renders a React component but also exports a value that is imported by a **non-React component**. For example, maybe your component also exports a constant, and a non-React utility module imports it. In that case, consider migrating the query to a separate file and importing it into both files. This will re-enable Fast Refresh to work. Other cases can usually be solved in a similar way.

Expand Down

0 comments on commit e83564c

Please sign in to comment.