docs(docs): close React Native happy-path gaps found validating NT-3951 - #433
Merged
Felipe Mamud (fmamud) merged 1 commit intoAug 13, 2026
Merged
Conversation
Add a Confirm in Live Events production check (with the in-app preview panel as an accepted alternative) and a standalone useOptimizedEntry() example alongside the existing OptimizedEntry and useEntryResolver() examples.
Charles Hudson (phobetron)
approved these changes
Aug 13, 2026
Felipe Mamud (fmamud)
deleted the
docs/nt-3951-react-native-happy-path-gaps
branch
August 13, 2026 15:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-completeness gap-check against NT-3951's acceptance criteria found two gaps in the React Native SDK guide:
useOptimizedEntry()) — only a one-line prose mention, unlike its sibling APIs (OptimizedEntry,useEntryResolver()) which both had full examples. Added a standalone code example for parity.The other 8 acceptance criteria (including AC4, Contentful entry fetching) were already fully documented with no stale APIs.
Test plan
pnpm exec prettier --write— no changespnpm guides:check— passpnpm knowledge:check— passRelated: NT-3951