Repository navigation
docs(mosaic): document Flow for moving between screens on one surface - #10584
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 35de167 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
No actionable comments were generated in the recent review.
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Description
Agent docs for Mosaic never mentioned the
Flowcomponent, and the skill only used "flow" to mean the model/controller/view split. Nothing pointed to the component when one screen replaces another on the same card or dialog. #10502 hit this:OrganizationListopens create-organization with an early return, so the screen pops in.mosaicskill now explains both meanings of "flow".packages/mosaic/AGENTS.mdadds a reuse-table row and a warning sign for conditional screen swaps.packages/mosaic/docs/views.mdadds a section on usingFlow: the card sits outside it, a step renders only its contents, and how nesting, direction and focus work. Loading, error and skeleton states can stay conditionals.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change