Repository navigation
Conversation
The settings schema of the schemaForm block takes only intl, so the @blocks-schema endpoint of Volto can build it outside the editor. The fields that depend on the block's own settings are now applied in the editor by applySchemaFormConditions. A registry override of the email defaults still takes precedence over the block defaults. Adds docs.block.md with the stored settings, the schema of the fields and a complete example. Moves the development setup from Volto 19.1.4 to 19.7.0 and adds the webpack catalog override. The README notes that the endpoint needs Volto 19.6 or later. Refs #29
sneridagh
approved these changes
Nov 12, 2026
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.
This adds support for the
@blocks-schemaendpoint of Volto 19.6 to the form block (schemaForm), so agents and generated reference documentation can read how its data is written.docs.block.mddocuments the data the block stores: the form's own settings and the JSON schema of its fields, with a complete example of a working form.intl, and the fields that depend on the block's own settings are applied in the editor, so the endpoint can build the schema.@blocks-schemasupport needs Volto 19.6 or later, and older versions ignore the file.The settings-dependent visibility and requirements moved from the schema into
applySchemaFormConditions, which the editor uses, so the editor behaves as before. The email defaults still come from the registry when a site sets them. Unit tests cover the schema called with onlyintland the editor conditions; the endpoint tests fail on the previous schema.Closes #29