From 3b060b4cbabf957aa5bde21d1946bc74b11da959 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rub=C3=A9n=20Norte?= Date: Wed, 8 Jul 2026 07:16:39 -0700 Subject: [PATCH] Fix markdown formatting in react-native-fantom docs README Summary: `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 --- private/react-native-fantom/__docs__/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/private/react-native-fantom/__docs__/README.md b/private/react-native-fantom/__docs__/README.md index d5997c130e8..dbfb007c8c1 100644 --- a/private/react-native-fantom/__docs__/README.md +++ b/private/react-native-fantom/__docs__/README.md @@ -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