TYPO3 Budget Ideas 2026 Round 1: Content Blocks JSON Schema Validation

[nhovratov]

No description provided.

[jonaseberle]

Cool stuff, thank you!

I've had it moan about a regex validation when including a Basic: (misses the /)

[nhovratov]

Cool stuff, thank you!

I've had it moan about a regex validation when including a Basic: (misses the /)

Basics not yet implemented, but will come soon!

Edit: Will fix the regex for identifier, but only for type Basic then. Thanks!

I wonder, some also use dash "-" in their identifier. But we do not recommend it. Not sure if this should fail with hard validation error. But maybe it should, as it might cause serious problems in DB level.

[sbuerk]

@nhovratov I'm pretty sure you have it on the todo list, just wanted to document it that it does not get forgotten:

This comes with an additional dependency not available in the core, which means that this needs to be bundeld for classic mode (TER) during tailor artifact building and uploading,
otherwise it would faile because opis/json-schema is not available (and it's a hard requirement and not a development dependency).

=> bundling & ensuring autoloading (namespaces).

[nhovratov]

@sbuerk

I'm pretty sure you have it on the todo list, just wanted to document it that it does not get forgotten:

This comes with an additional dependency not available in the core, which means that this needs to be bundeld for classic mode (TER) during tailor artifact building and uploading, otherwise it would faile because opis/json-schema is not available (and it's a hard requirement and not a development dependency).

=> bundling & ensuring autoloading (namespaces).

I don't think this feature is very useful for classic installations, as they usually don't have a CI pipeline to run it.
Is it possible to upload to TER with a missing dependency? This should only fail on runtime, if users try to run the command. I could maybe even catch this with a "class_exists" and print "command does not work in non-composer mode" or something like that.