Skip to content

feat: export schema API for building custom tools and add richText lexical features to schema#2

Merged
jhb-dev merged 1 commit into
mainfrom
feat/plugin-schema-api
May 31, 2026
Merged

feat: export schema API for building custom tools and add richText lexical features to schema#2
jhb-dev merged 1 commit into
mainfrom
feat/plugin-schema-api

Conversation

@jhb-dev

@jhb-dev jhb-dev commented May 31, 2026

Copy link
Copy Markdown
Contributor
  • feat: the plugin entry now exports the schema API for building custom tools (e.g. listEntities + getEntitySchema + getBlockSchema MCP tools) without going through HTTP. listReadableEntities({ req }) returns the readable collection/global slugs plus localization; getEntitySchema({ req, type, slug }) returns the same { slug, fields, jsonSchema } the /schema endpoint produces for one entity; getBlockSchema({ req, slugs }) resolves richText block slugs to { slug, fields }.
  • feat: schema endpoint now reports the enabled Lexical nodes of each richText field under a lexicalFeatures key, organized by where each node lives in richtext JSON. Every key is the exact node type to emit, so agents know what a field accepts before authoring. Surfaces in _schema.json.
  • breaking: renamed the exported extractFields to toFieldSchemas

@jhb-dev jhb-dev merged commit f211bd5 into main May 31, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant