Block -> JSON Schema?

[ddebowczyk]

Do you plan to support generating JSON Schema for Block?

[roberto-butti]

Good point @ddebowczyk .
Something about validating the structure, and one of the options I want to use is validating through a JSON schema.
But with your question, do you mean generating a JSON schema from an existent Block structure?
I will think about some real use-case scenarios.

[ddebowczyk]

Yes, I mean generating JSON Schema from block structure.

[roberto-butti]

Thanks for the suggestion.

JSON Schema validation fits naturally within Data Block’s scope: a Block contains data, and validating that data against an explicitly defined contract is part of safely handling it.

Generating (or, more accurately, inferring) a JSON Schema from sample data is a different responsibility. A sample cannot reliably express business rules such as optional properties, allowed ranges, string formats, homogeneous arrays, or whether additional properties should be accepted. Supporting this properly would require Data Block to define and maintain many inference policies beyond its core purpose.

For this reason, I prefer to keep validation in Data Block while leaving schema inference to specialized libraries. One PHP package designed for this use case is ropi/json-schema-generator:

https://github.com/ro-pi/json-schema-generator

Data Block can already provide its contents through toJsonObject() or toArray(), making integration with an external inference library straightforward.

Therefore, I’m closing this issue as out of scope for the core package. We could still document integration with a schema-inference library in the future if there is sufficient interest.

Thanks again for raising the idea. It helped clarify the boundary between schema validation and schema inference.