docs(webviewer): add Initial Props page#278
Conversation
Document the pull-not-push pattern for bootstrap data: web viewer fetches initial props via fmFetch once mounted, rather than FileMaker pushing via HTML substitution or PerformJavaScriptInWebViewer (which races the bundle load). Includes initial-route and current-user examples. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@proofkit/better-auth
@proofkit/cli
create-proofkit
@proofkit/fmdapi
@proofkit/fmodata
@proofkit/typegen
@proofkit/webviewer
commit: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request adds documentation for the initial props bootstrap pattern used in the Web Viewer. It explains how to implement a pull-based startup flow where the web app fetches and validates FileMaker data via ChangesInitial Props Documentation
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
Summary
/docs/webviewer/initial-propscovering the pull-not-push pattern for bootstrap data.fmFetchto ask for props once loaded, rather than FileMaker pushing them in via HTML substitution orFileMaker.PerformJavaScriptInWebViewer(both race the bundle load).meta.jsonunder Concepts, betweencommandsandplatform-notes.Test plan
pnpm run cipassesSummary by CodeRabbit