Files
zeekay 29fc919f95 fix: repair core-import specifiers + install fixes
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]
2026-07-01 18:10:37 -07:00

40 lines
1.1 KiB
TypeScript

import type { CollectionConfig } from '@hanzo/cms'
import { BlocksFeature, lexicalEditor } from '@hanzo/cms-richtext-lexical'
import { lexicalViewsNestedSlug } from '../../slugs.js'
import { lexicalNestedBlocks } from './blocks.js'
/**
* Collection to test that nested richtext fields keep their ViewSelector
* when parent richtext has NO views configured.
*
* Structure:
* - Parent richtext: lexicalEditor() with NO views
* - Block inside parent: contains richtext WITH views
*
* Expected: Block's richtext should show ViewSelector (not inherited, parent has nothing to pass down).
*/
export const LexicalViewsNested: CollectionConfig = {
slug: lexicalViewsNestedSlug,
fields: [
{
name: 'parentRichText',
type: 'richText',
editor: lexicalEditor({
features: ({ defaultFeatures }) => [
...defaultFeatures,
BlocksFeature({
blocks: lexicalNestedBlocks,
}),
],
// NO views configured on parent
}),
},
],
labels: {
plural: 'Lexical Views Nested',
singular: 'Lexical Views Nested',
},
}