nhovratov / content-blocks-json-schema Goto Github PK

Also check, if https://docs.typo3.org/p/contentblocks/content-blocks/main/en-us/YamlReference/ContentTypes/RecordTypes/Index.html#record-type-fallbacklabelfields could be optimized. The JSON Schema should make a hint, when there are more than one labelFields used.

I am not sure if it is even possible to do that inside a JSON Schema.

File -> "allowed" does not seem to work as expected in the IDE, I don't get any completion for the enum common-image-types, etc.

This is the epic ticket for creating all the different schemas.

The most of the following list is already implemented. I still create this list so we have an overview of all types. Maybe we can remove some of the following but at the moment it is a 1:1 list of all available types.

• general content element schema
• record types
• page types
• general field types

Field Types

• Basic -> not needed
• Category
• Checkbox
• Collection
• Color
• DateTime
• Email
• File
• #3
• Folder
• Json
• Language
• Linebreak
• Link
• Number
• Palette
• Password
• Radio
• Relation
• Select
• Slug
• Tab -> not needed
• Text
• Textarea
• Uuid

https://docs.typo3.org/p/contentblocks/content-blocks/main/en-us/YamlReference/Root/Index.html#confval-root-vendorprefix

https://docs.typo3.org/p/contentblocks/content-blocks/main/en-us/YamlReference/Basics/Index.html

When you use basics, you use a slash inside the identifier, this is not allowed at the moment. The regex needs to be adjusted.

Using PHPStorm 2024.1.4 even a very simple content block will trigger a validation error for "required property fields". Indeed this poperty is not required at this point.

Not sure if PHPStorm is messing up as the only property fields I can see in the schema that is required should only be required for flexforms.