mirror of
https://github.com/facebook/react-native.git
synced 2026-11-18 20:19:07 +00:00
Fix markdown formatting in react-native-fantom docs README (#57486)
Summary: Pull Request resolved: https://github.com/react/react-native/pull/57486 `prettier --list-different` (run via `yarn format-check`) flagged the react-native-fantom `__docs__/README.md` as unformatted. Re-wrap the two affected prose lines to prettier's print width so the docs pass the formatting check. No content changes; formatting only. Changelog: [Internal] ___ Differential Revision: D111041556 fbshipit-source-id: cab15f502e941d908503e0873fe8cba12b48686f
This commit is contained in:
1 parent
a69badd468
commit
0df0be24ef
1 file changed
+4
-4
@@ -187,12 +187,12 @@ hi
|
||||
underlying native (Fabric/TurboModules) code, so tests stay close to real
|
||||
usage and are more resilient to internal refactors. Observe results through
|
||||
the public surface too — e.g. assert the rendered output
|
||||
(`root.getRenderedOutput(...)`) or values delivered to public listeners
|
||||
rather than reading private state.
|
||||
(`root.getRenderedOutput(...)`) or values delivered to public listeners rather
|
||||
than reading private state.
|
||||
- When Fantom doesn't support something (a native module, a capability, a way
|
||||
to observe a result, etc.), it's fine to reach into internals to work around
|
||||
that limitation. Prefer a short comment explaining why the internal access is
|
||||
necessary.
|
||||
that limitation. Prefer a short comment explaining why the internal access
|
||||
is necessary.
|
||||
- Place test files in `__tests__` directories alongside the code being tested.
|
||||
- Benchmark tests use the `-benchmark-itest.js` suffix.
|
||||
- Use `Fantom.runTask()` to render and run synchronous operations; it ensures
|
||||
|
||||
Reference in new issue
Block a user