feat: export schema API for building custom tools and add richText lexical features to schema#2
Merged
Merged
Conversation
…xical features to schema
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
listEntities+getEntitySchema+getBlockSchemaMCP 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/schemaendpoint produces for one entity;getBlockSchema({ req, slugs })resolves richText block slugs to{ slug, fields }.richTextfield under alexicalFeatureskey, organized by where each node lives in richtext JSON. Every key is the exact nodetypeto emit, so agents know what a field accepts before authoring. Surfaces in_schema.json.extractFieldstotoFieldSchemas