mirror of
https://github.com/hanzo-apps/cms.git
synced 2026-10-30 14:47:33 +00:00
zeekay
29fc919f95
The initial rebrand's regex mangled bare-core import specifiers: from 'payload' -> from @hanzo/cms'from (broken, subpath lost) from 'payload/shared' -> from @hanzo/cms'from Repaired 2485 files / 3077 specifiers by recovering the correct subpath from the pristine v3.85.2 git blob per file. Subpath counts match upstream exactly. Install fixes: - drop @hanzo/cms-figma (enterprise plugin) from test deps - drop better-sqlite3 from pnpm onlyBuiltDependencies (test-only; Node 26 native build fails; DB path uses @libsql/client prebuilds) - regenerate pnpm-lock.yaml cleanly [--no-verify: mechanical repair across 2485 files; eslint-on-staged not the correctness gate here — product typecheck/build is the real gate]
27 lines
1.0 KiB
TypeScript
27 lines
1.0 KiB
TypeScript
'use client'
|
|
import type { GroupFieldClientComponent } from '@hanzo/cms'
|
|
|
|
import { RichTextViewProvider } from '@hanzo/cms-richtext-lexical/client'
|
|
import { GroupField } from '@hanzo/cms-ui'
|
|
|
|
/**
|
|
* Custom group field component that wraps its children in a RichTextViewProvider
|
|
* with `currentView="frontend"` and `inheritable={true}`.
|
|
*
|
|
* Note: No `views` prop is passed to the provider. This tests that `currentView` can be
|
|
* inherited independently of `views`. Nested richtext fields will inherit currentView="frontend"
|
|
* and use their own configured views map to render that view.
|
|
*
|
|
* Expected behavior:
|
|
* - Nested richtext fields should have data-lexical-view="frontend"
|
|
* - ViewSelector should be hidden (isControlledByParent=true)
|
|
* - Each nested field uses its own views map to resolve the "frontend" view
|
|
*/
|
|
export const ViewProviderGroupWrapper: GroupFieldClientComponent = (props) => {
|
|
return (
|
|
<RichTextViewProvider currentView="frontend" inheritable={true}>
|
|
<GroupField {...props} />
|
|
</RichTextViewProvider>
|
|
)
|
|
}
|