feat(example): restore the example app to a plain SDK showcase (YPE-3713) - #121
Merged
Conversation
…3713) The example app had accumulated demo scaffolding around the highlights epic. Strip it back so a partner evaluating the SDK sees the components as they would use them, not a development harness. - The Bible tab is `<BibleReader />` again. The custom copy/share toggle and the selection status bar were wired to the same block of state (`onVerseSelect`, `clearSelectionSignal`, `onCopy`, `onShare`), so they come out together. The reader still owns the verse action sheet, which falls back to `expo-clipboard` and RN `Share` on its own. - Delete the `highlight-flow` tab and its harness. It existed to reach the permission flow before the reader could (YPE-3709 subtask 3); the reader now drives the whole flow, so it only duplicated coverage that lives in unit tests. `expo-clipboard` stays in the example's dependencies — it is a UI peer for the action sheet's Copy button, not just the removed override. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dustin-Kelley
marked this pull request as ready for review
August 6, 2026 20:20
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
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.
Part of YPE-3713. The example app picked up demo scaffolding while the highlights epic was in flight. This strips it back so a partner evaluating the SDK sees the components as they would actually use them.
What changed
The Bible tab is
<BibleReader defaultVersionId={3034} />again. The custom copy/share toggle and the "Tap a verse to open the action sheet" status bar were driven by one block of demo state —onVerseSelect,clearSelectionSignal,onCopy,onShare, and theuseCustomActionsswitch — so removing either meant removing both. The file is now byte-identical to its pre-epic state.This does not change what the app demonstrates. The reader owns the verse action sheet, so tapping a verse still gives you the reference, the highlight swatches, Copy, and Share — now through the SDK's own
expo-clipboardand RNSharefallbacks rather than the example's overrides.The
highlight-flowtab is deleted, along with itsNativeTabs.Trigger. It was the temporary harness from YPE-3709 subtask 3, built to reach the permission flow before the reader could subscribe it. The reader drives the whole flow now, so the harness only exercised in isolation whatbible-reader-highlights-prompts.test.tsxalready covers. Its own header comment scheduled it for deletion here.AGENTS.mdloses the bullet describing the harness and deferring its removal to this ticket — it would otherwise point at a file that no longer exists.What was deliberately left alone
expo-clipboardstays inapps/example/package.json. It is a peer dependency of the UI package for the action sheet's built-in Copy button, so dropping it with the override would break Copy rather than clean anything up.The provider still requests
permissions: ['highlights']. That is AC 1 of YPE-3713 and it is what gives the showcase real highlight data to paint.Note for review
Nothing in the example exercises the
onCopy/onShareoverrides orclearSelectionSignalanymore. They stay covered by unit tests inpackages/ui, and the README snippet is now the only place a partner sees that Copy and Share are overridable. Flagging in case you would rather that live in the app.Verification
pnpm lint,pnpm typecheck(including the example's owntsc --noEmit, which confirms no stale generated route types), andpnpm test(306 passed, 1 skipped) all pass. Device verification for the epic's remaining ACs is separate from this cleanup.🤖 Generated with Claude Code
Greptile Summary
Restores the example application to a focused, partner-facing SDK showcase.
BibleReaderexperience directly.Confidence Score: 5/5
The PR appears safe to merge, with the removed example scaffolding fully covered by SDK-owned behavior and no stale route references.
The BibleReader independently manages verse selection, action-sheet dismissal, Copy/Share fallbacks, and highlight prompts; the deleted harness has no remaining callers, and the profile and provider edits preserve existing behavior.
Important Files Changed
Reviews (1): Last reviewed commit: "refactor(example): clean up layout and p..." | Re-trigger Greptile
Context used: