Skip to content

spec(List): React Native platform record - #12819

Draft
imdreamrunner wants to merge 4 commits into
chore/knowledge-react-native-platform-recordsfrom
spec/list-react-native-record
Draft

imdreamrunner wants to merge 4 commits into
chore/knowledge-react-native-platform-recordsfrom
spec/list-react-native-record

Conversation

@imdreamrunner

@imdreamrunner imdreamrunner commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #12592 (it lets check:knowledge accept react-native platform records); the base is that branch. This PR's change is one file: docs/specs/components/List/List.react-native.spec.md.

Exact decision needed

How React Native renders List: which web props it takes, what it adds, who scrolls it and how it windows long collections. The record is the React Native platform record of component:List (component:react-native/List, platform_of: component:List). It states only what React Native adds or does differently.

Existing authority searched

  • Records: component:List (FR1–FR13, DEC-1–DEC-6); component:ListItem and its Swift record; component:Item; architecture:container-padding (host padding and the edge vocabulary); architecture:knowledge-contracts (platform records beside the core record); spec:AST-082 FR3, FR5, FR7 and spec:AST-093 FR1–FR5 (core and platform contracts, native-first, theme values); the open drafts spec:AST-124 (the pinch around a scroller, FR17 and DEC-6; the swipe row, FR6), spec:AST-125 (the screen's scroll target) and the other React Native platform records (spec(TabBar): React Native platform record #12686, spec(TopNav): React Native platform record #12685, spec(FileInput): React Native record with the photo library source #12597).
  • Code: packages/core/src/List/ (props, edge treatments, defaults).
  • Overlap: no other record owns List on React Native. spec:AST-124 FR17 leaves the pinch's public face to the List record; FR13 states it. Row behaviour stays with ListItem and Item.

Decision

  • React Native takes web's children, density, hasDividers, edge, edgeCompensation and header. It does not offer xstyle, animatedLayout, reorderable, listStyle or start; rows change at once, as web's List does without a handle (FR1).
  • React Native adds density="table", variant (insetGrouped), dividerInset, footer, rowMinHeight and data mode (FR2). Divider colour comes from the theme. Two gap lines record that the package spells dividerInset as separatorInset and also offers a per-call-site separatorColor.
  • edge places rows as component:List FR3–FR6 and FR8 define, bleed included (FR3). Three gap lines record where React Native falls short: bleed content off the host content line, no inset from BottomSheet, and square corner rows.
  • Dividers inset per row by default (FR5, DEC-3). insetGrouped draws the platform's grouped list in color.backgroundSurface on color.backgroundBody, and ListGroupedPage owns the page edge (FR6, DEC-4). One gap line records that the package steps the grouped page darker than any theme value where the body sits too close to the surface.
  • Inside a vertical scroller the List draws in flow; elsewhere it is its own scroller and windows its rows, in children mode and data mode alike (FR8, FR9, DEC-2).
  • Long collections are List's data mode, not a second component (FR10, DEC-1). It has a scroll handle that draws its target rows in the same render (FR11), takes the screen's scroll props (FR12) and keeps its scroller inside a pinch (FR13).
  • Accessibility: a list whose every row is one screen-reader stop, recycled rows read in order, a focused row kept through a reader's scroll, and text-size growth (AR1–AR5).

Rejected alternatives

None recorded.

Claim scope and non-goals

The claims are FR1–FR13, AR1–AR5, ORD1–ORD4, PR1–PR4 and DEC-1–DEC-4. The record's "Does not own" list names the owner of each adjacent responsibility.

Open question:

  • OQ1 (human-api): whether React Native List offers listStyle and start.

Evidence and implementation relationship

No React Native implementation exists in this repository. The record states the target behavior, and its verification map names the evidence for each requirement: unit tests of the package, Simulator and emulator captures, a scroll benchmark on device builds, and VoiceOver and TalkBack checks. Where the behavior does not meet the target, the record lists a requirement gap line (FR2, FR3, FR6).

Writing rubric results

  • R1 narration: none; every requirement is in the present tense about the system.
  • R2 research in the record: none; the conclusions sit inside DEC-1 to DEC-4.
  • R3 evidence naming a change: none; basis cells cite records, clauses and platform guidance.
  • R4 rejected alternatives over one line or outside a decision: none; the record has no rejected alternatives.
  • R5 pull request or issue references remaining: none.
  • R6 ruled open questions still listing options: none; the scroll owner, data mode, the default divider inset and the grouped page edge are decisions. OQ1 is unanswered and keeps its two options.
  • R7 project status: none in prose; six shortfalls are requirement gap lines under FR2, FR3 and FR6. The only lifecycle field is the template's Released default preserved.

Scope

Components: List

  • This PR contains specification records only.
  • It records observable behavior and preserves equivalent internal implementations.
  • Any named internal mechanism is intentionally public, names its dependent caller/system, and explains why an equivalent implementation would not satisfy the contract.
  • Verification states the evidence layer and failure signal without prescribing CI job/workflow topology.
  • It records one intentional durable decision, not a rescue for a separable tagalong.
  • The canonical knowledge owner, affected current claims, and overlapping open work are named; any ownership collision is resolved or called out for human decision.
  • Adjacent API, visual, accessibility, composition, and implementation facts remain outside scope unless this exact decision depends on them.
  • Public text and artifacts contain no internal Meta context.

Validation

  • node scripts/check-knowledge.mjs: passes ("Knowledge templates and records are aligned.")
  • Prettier: passes
  • git diff --check: clean

@vercel

vercel Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
astryx Ready Ready Preview Nov 19, 2026 7:26am UTC

Request Review

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Meta Open Source bot. label Nov 19, 2026
@astracat-bot

astracat-bot Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

AI review status for this pull request.

Review status Updated
❓ Needs maintainer input (for maintainers only) Nov 19, 2026, 7:34 AM UTC

@astracat-bot astracat-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval waits on an engineering owner's decision, because this draft record adds requirements (FR1–FR13, AR1–AR5 and DEC-1–DEC-4) that no current spec states. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner.

Three fixes are needed whatever the decision:

  • FR3 defines bleed so row text sits at the row's own inset from the host's padding edge, while component:List FR5 and DEC-4 keep it on the host content line, give the first and last rows a rounded host's corner and admit BottomSheet as a host, so state bleed as component:List FR5 does and keep the three gap lines as gaps against it.
  • separatorColor lets each call site pick the divider colour, a visual prop for one platform that spec:AST-093 FR4 and spec:AST-082 DEC-2 rule out, so take the divider colour from the theme instead.
  • separatorInset and separatorColor introduce "separator" for what Astryx calls dividers (hasDividers, hasDivider, Divider), against architecture:public-component-api INV2, so name them with divider, for example dividerInset.

FR12 and FR13 also cite spec:AST-124 and spec:AST-125, which are not in the repository yet, so they resolve only once those drafts land.

Claims and files checked

Review mode: full; reason: no-earlier-review

  • Claim: the pull request is stacked on the knowledge-tooling pull request and changes one file. Verified: the record is the only changed file, and the base is that pull request's single commit.
  • Claim: that pull request lets the knowledge check accept React Native records. Verified: it adds react-native to the accepted platform languages.
  • Claim: the record states only what React Native adds or does differently. False for FR3, which restates bleed differently from the core record.
  • Claim: the listed existing authority exists, with AST-124, AST-125 and the other React Native records as open drafts. Verified.
  • Claim: no other record owns List on React Native, and AST-124 FR17 leaves the pinch's public face to the List record. Verified.
  • Claim: edge moves row frames as web's treatments define. False for bleed (FR3).
  • Claim: no React Native implementation exists in the repository. Verified: the native package has no React Native binding.
  • Claim: the verification map names evidence for each requirement. Mostly verified: PR1 has no row.
  • Claim: gap lines mark where behaviour misses the target. False: the FR3 gap lines describe what FR3's own text requires.
  • Claim: the writing rubric finds no narration, research, change references or project status. Verified: status appears only in template fields and the FR3 gap lines.
  • Claim: public text holds no internal context. Verified.
  • Claim: the knowledge check, Prettier and the whitespace check pass. Verified at this head.
  • File: docs/specs/components/List/List.react-native.spec.md. The three findings above; consistent with the base branch's tooling.

Automated review (maintainer link)

@astracat-bot astracat-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval waits on an engineering owner's decision, because this draft record adds requirements (FR1–FR13, AR1–AR5 and DEC-1–DEC-4) that no current spec states: the React Native additions, scroll ownership and data mode, the divider inset and dark divider colour, the grouped list, Android's guideline choice, and FR12–FR13, which rest on the open AST-124 and AST-125 drafts. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. This revision fixes the earlier bleed, separatorColor and divider-name findings; one fix stands whatever the owner decides:

  • FR6 and the theme values list read a grouped card colour and a grouped page colour that no theme defines, while spec:AST-093 FR4 requires every value to come from the theme, so name existing theme values, the platform's own grouped colours, or a defineNativeTheme entry.

Two smaller points:

  • FR3's opening sentence ("keeping the row's own inline inset inside it") still describes the old bleed geometry that its own bleed clause and first gap line rule out; scope it to flush and outset.
  • The five gap lines describe "the package", which this repository does not contain; name it or drop the lines until its code is here.
Claims and files checked

Review mode: full; reason: spec-record

  • Claim: the pull request is stacked on the change that lets the knowledge check accept React Native platform records, with that branch as its base: verified.
  • Claim: the change is one file: verified.
  • Claim: the listed authority was searched (List, ListItem and its Swift record, Item, container padding, knowledge contracts, AST-082, AST-093, the open AST-124 and AST-125 drafts and the other React Native records): verified; each exists as described and the drafts are open.
  • Claim: no other record owns List on React Native: verified.
  • Claim: the web props kept and not offered (FR1): verified.
  • Claim: the React Native additions, the theme divider colour and two FR2 gap lines: verified.
  • Claim: edge follows core FR3–FR6 and FR8, bleed included, with three FR3 gap lines: verified, with the FR3 note above.
  • Claim: the divider inset default, the grouped list and page edge, scroll ownership, data mode, the handle, the scroll props, the pinch and AR1–AR5: verified as stated in the record.
  • Claim: the claim scope (FR1–FR13, AR1–AR5, ORD1–ORD4, PR1–PR4, DEC-1–DEC-4) and the one open question: verified.
  • Claim: no React Native implementation exists in this repository: verified; the gap lines that describe one are the note above.
  • Claim: rubric results R1–R7: verified against the record.
  • Claim: the knowledge check, Prettier and the whitespace check pass: verified on this revision.
  • File: docs/specs/components/List/List.react-native.spec.md: one blocking finding (FR6 grouped colours) and two notes.

Automated review (maintainer link)

@astracat-bot astracat-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval waits on an engineering owner's decision, because this draft record adds requirements (FR1–FR13, AR1–AR5 and DEC-1–DEC-4) that no current spec states: the React Native additions, scroll ownership and data mode, the divider inset and dark divider colour, the grouped list and its colours, Android's guideline choice, and FR12–FR13, which rest on the open AST-124 and AST-125 drafts. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. This revision fixes the earlier grouped-colour finding: FR6 now names color.backgroundSurface and color.backgroundBody, which the native theme defines. Nothing else blocks; four smaller points:

  • FR6 draws the iOS card with no frame, so in the Chocolate light theme and both Gothic modes, where those two colours are identical, the card does not show; say what the card does there, so the package does not need the off-theme page colour the new FR6 gap line describes.
  • The Contract at a glance row still says "Gap lines under FR2 and FR3"; add FR6.
  • FR3's opening sentence ("keeping the row's own inline inset inside it") still describes the old bleed geometry that its own bleed clause and first gap line rule out; scope it to flush and outset.
  • The six gap lines describe "the package", which this repository does not contain; name it or drop the lines until its code is here.
Claims and files checked

Review mode: full; reason: spec-record

  • Claim: the pull request is stacked on the change that lets the knowledge check accept React Native platform records, with that branch as its base: verified.
  • Claim: the change is one file: verified.
  • Claim: the record is the React Native platform record of List and states only what React Native adds or does differently: verified (id, platform_of and Ownership boundary).
  • Claim: the listed authority was searched, and the gestures draft leaves the pinch's public face to the List record: verified; each record exists as described, the drafts are open, and the gestures draft's pinch requirement says the List and ScrollView records decide its public face.
  • Claim: no other record owns List on React Native: verified.
  • Claim: the web props kept and not offered (FR1): verified.
  • Claim: the React Native additions, the theme divider colour and the two FR2 gap lines: verified.
  • Claim: edge follows the core record's edge requirements, bleed included, with three FR3 gap lines: verified, with the FR3 note above.
  • Claim: per-row divider insets, the grouped list in the theme's surface colour on its body colour, the page edge, and one FR6 gap line: verified, with the FR6 note above.
  • Claim: scroll ownership, windowing, data mode, the handle, the screen's scroll props, the pinch and AR1–AR5: verified as stated in the record.
  • Claim: no rejected alternatives are recorded: verified.
  • Claim: the claim scope (FR1–FR13, AR1–AR5, ORD1–ORD4, PR1–PR4, DEC-1–DEC-4) and the one open question: verified.
  • Claim: no React Native implementation exists in this repository, and the verification map names evidence for each requirement: verified; the gap lines that describe an implementation are the last note above.
  • Claim: rubric results R1–R7, including six gap lines under FR2, FR3 and FR6: verified against the record.
  • Claim: public text contains no internal context: verified.
  • Claim: the knowledge check, Prettier and the whitespace check pass: verified on this revision.
  • File: docs/specs/components/List/List.react-native.spec.md: no blocking finding; four non-blocking notes.

Automated review (maintainer link)

| FR3 | `edge` MUST place rows as `component:List` FR3–FR6 and FR8 define: each row's frame moves outward on both inline edges, keeping the row's own inline inset inside it. `flush` moves it by the row's inset, with the list clipping at its edges so row paint stops on the content line; `outset` by the smaller of the row's inset and the host's, so content reaches the host content line when the host inset is at least the row's; `bleed` to the host's padding edge, with square rows, except that, when the list is a rounded host's first or last child, its first or last row takes that host's corner less the host block padding it keeps, and with row content on the host content line, or at the row's own inset from its edge when the host inset is smaller. The row's inset is the inline padding of its density, the value Item applies. The host inset is the padding the nearest eligible host publishes, the content area of a Card, Section, Dialog or BottomSheet among them (`component:List` FR8); with none, `outset` and `bleed` place rows as `padded`. | `component:List` FR3–FR6, FR8, DEC-4; `architecture:container-padding` INV6, INV9 | verify |
| FR4 | Rows MUST take the list's density. Without dividers rows stand `space.s0_5` apart; with dividers they touch, and a divided or `bleed` List draws square rows whose press fill reaches the row's edges. The header sits `space.s2` above the rows and the footer `space.s2` below them. `table` rows sit at `space.s4` from the row's edge and are at least the platform's minimum touch target tall (44 pt on iOS, 48 dp on Android), grown with the text size. | `component:List` FR2; `spec:AST-093` FR2 | verify |
| FR5 | With `hasDividers`, `dividerInset` MUST place each divider: `full` across the row, as on the web; `text` from the row's text, past any start content or glyph, to the row's trailing content margin; `content` inset by the density's inline padding at both ends, so it holds for any row content from the first frame; `auto` as `text` for a row with a leading glyph or start content and as `content` for any other, each row drawing the line at its own bottom so the upper row of a boundary decides, with none under the last row; `none` no divider, with rows still square. Insets are logical, so they mirror in right-to-left. Without `hasDividers` no divider draws. A divider is `size.borderWidth` in the theme's divider colour: the border colour, `color.borderEmphasized` in dark. | DEC-3; Apple Human Interface Guidelines, Lists and tables | verify |
| FR6 | `variant="insetGrouped"` MUST draw the rows in a rounded card (`radius.container`, `color.backgroundSurface`, clipped at its corners) on the screen's grouped page in `color.backgroundBody`, with square, gapless rows and the header and footer outside the card on the rows' text line as secondary words; the header is the body size on iOS and supporting text elsewhere, and string words are a heading for assistive technology. `edge` does not apply. On iOS the List insets itself from its container's edges by the system layout margin (16 pt in windows narrower than 414 pt, 20 pt from 414) and its rows are at least 52 pt tall at the default text size, and the card draws no frame; on Android the card draws a hairline frame in the divider colour only where its surface is faint against the page. `ListGroupedPage` holds several grouped Lists on one vertical scroll in `color.backgroundBody`, `space.s6` apart and from its ends, padding the screen gutter (`space.s4`) on Android and nothing on iOS; horizontal padding or margin in its content style is ignored with one development warning. `useGroupedListMetrics`, `ListGroupedHeader` and `ListGroupedFooter` give the same metrics and parts to a page that windows its own rows. | DEC-4; Apple Human Interface Guidelines, Lists and tables; Material 3 lists | verify |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking: on iOS this card draws no frame, so it shows only where color.backgroundSurface differs from color.backgroundBody. In the Chocolate theme's light mode and both Gothic modes the two are identical (1.00:1), and the card disappears; the new FR6 gap line has the package step the page outside the theme there, which spec:AST-093 FR4 rules out. Consider saying what the card does when the colours match (Android's faint-surface hairline on iOS too, the platform's grouped colours under spec:AST-093 FR3, or a flat group).

@astracat-bot astracat-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval waits on an engineering owner's decision, because this draft record adds requirements (FR1–FR13, AR1–AR5 and DEC-1–DEC-4) that no current spec states: the React Native additions, scroll ownership and data mode, the divider inset and dark divider colour, the grouped list and its colours, Android's guideline choice, and FR12–FR13, which rest on the open AST-124 and AST-125 drafts. An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. This revision fixes the three earlier notes on the glance row, FR3's opening sentence and the unnamed library. Nothing blocks; two smaller points:

  • FR12 now says the surrounding scroller takes the screen's scroll props in flow, but not what the List does with its own scrollProps there; the verification map has it drop them while the record rejects a prop accepted and ignored, so say that the List leaves them unapplied and warns once in development.
  • FR6 draws the iOS card with no frame, so in the Chocolate light theme and both Gothic modes, where the surface and page colours are identical, the card does not show; say what the card does there, so the library does not need the off-theme page colour the FR6 gap line describes.
Claims and files checked

Review mode: full; reason: spec-record

  • Claim: the pull request is stacked on the change that lets the knowledge check accept React Native platform records, with that branch as its base: verified.
  • Claim: the change is one file: verified.
  • Claim: the record is the React Native platform record of List and states only what React Native adds or does differently: verified (its id, its platform link and its ownership boundary).
  • Claim: the listed authority was searched, and the gestures draft leaves the pinch's public face to the List record: verified; each record exists as described, the drafts are open, and the gestures draft says the List and ScrollView records decide the pinch's public face.
  • Claim: no other record owns List on React Native: verified.
  • Claim: the web props kept and not offered (FR1): verified.
  • Claim: the React Native additions, the theme divider colour and the two FR2 gap lines about the library's separator names: verified.
  • Claim: edge follows the core record's edge requirements, bleed included, with three FR3 gap lines: verified.
  • Claim: per-row divider insets, the grouped list in the theme's surface colour on its body colour, the page edge, and one FR6 gap line: verified, with the FR6 note above.
  • Claim: scroll ownership, windowing, data mode, the handle, the screen's scroll props and the pinch: verified as stated, with the FR12 note above.
  • Claim: accessibility requirements AR1–AR5: verified as stated in the record.
  • Claim: no rejected alternatives are recorded: verified.
  • Claim: the claim scope (FR1–FR13, AR1–AR5, ORD1–ORD4, PR1–PR4, DEC-1–DEC-4) and the one open question: verified.
  • Claim: no React Native implementation exists in this repository, and the verification map names evidence for each requirement: verified.
  • Claim: rubric results R1–R7, including six gap lines under FR2, FR3 and FR6: verified against the record.
  • Claim: public text contains no internal context: verified.
  • Claim: the knowledge check, Prettier and the whitespace check pass: verified on this revision.
  • File: docs/specs/components/List/List.react-native.spec.md: no blocking finding; two non-blocking notes.

Automated review (maintainer link)

| FR9 | As its own scroller, List MUST mount only the rows near the viewport plus a draw distance, and a row that leaves the window gives its slot to the row that enters, so a scroll renders one slot per row instead of mounting one. `overscan` sets the draw distance in viewport heights each way; unset, it is a viewport each way at rest (at least 900 pt; 1,200 dp on Android) and a quarter second of travel ahead while scrolling (at most two viewports; on Android 0.35 s and three). A row's own state belongs to its item: a slot's content is keyed by `keyOf`, the element key in children mode, or the index, and starts fresh for each item unless `hasRowReuse` keeps the row's component across items. `itemHeight` places rows at exact offsets with no measuring, one number for every row or one per item; a result that is not a finite number of at least 0 measures that row, with one development warning. Unset, rows are measured, `estimatedItemHeight` (default: the touch floor grown with the text size) placing them first. `itemType` keeps each kind of row in slots of its kind. A removed child unmounts. | DEC-1 | verify |
| FR10 | With `data` and `renderItem`, List MUST draw one row per item in place of `children`. A row MUST be drawn again only when its item, its index, `renderItem`'s identity or `extraData` changes. `numColumns` draws equal cells per row, windowed, or as wrapping cells keyed by item in flow. `onRefresh` turns on pull to refresh, with `isRefreshing` showing it; `onEndReached` is called once each time the end of the data comes within a viewport, once per data length. | DEC-1 | verify |
| FR11 | In data mode as its own scroller, the List's ref MUST be a `ListHandle` whose `scrollToOffset`, `scrollToIndex` (with `viewPosition`) and `scrollToEnd` draw the rows at the target in the same render that moves the scroll, so a jump never shows undrawn rows, a jump made from a layout effect in the render that changes the rows included. On iOS `scrollToOffset` keeps an offset above 0 as given; `scrollToIndex`, `scrollToEnd` and every Android scroll stop at the top. In flow or in children mode the ref stays null. | DEC-1 | verify |
| FR12 | In data mode as its own scroller, `scrollProps` MUST reach the List's scroll view: the props a screen gives its body scroller (`useScreenScrollProps()`'s result fits), so a screen whose body is one List collapses its large title and minimizes its tab bar with it. The List composes its own handling with the given ref, `onLayout`, `onContentSizeChange`, `onScroll`, `onScrollEndDrag` and `onMomentumScrollEnd`; honours the content style's numeric padding; keeps its own refresh control when it has `onRefresh`, its list role and Android's nested scrolling; and gives the screen's `nativeID` precedence over `id`'s. A `style` holding Animated values runs on the UI thread and stays the screen's scroll view. In flow, the surrounding scroller takes the screen's scroll props. The List's scroller is the scroll source of content in its header that windows to the viewport. | `spec:AST-125` FR5, FR8; DEC-2 | verify |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking: this sentence says what the app does in flow, but not what the List does with its own scrollProps there. The verification map fails "scroll props applied in flow" (line 255), so a data-mode List inside a vertical ScrollView takes the prop and drops it, which the record's own checks reject as "a prop accepted and ignored" (lines 36 and 247). Consider: "In flow, the List leaves scrollProps unapplied and warns once in development; the surrounding scroller takes the screen's scroll props."

This branch was successfully deployed

1 active deployment
Preview — 2f5b26ee Deployed Nov 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant