The schema library provides the ability to define schemas with a declarative API and in turn using any of the processors to act on that schema.
We separate the concepts of the schema definition and the processors to allow us to build an AST describing a schema, and then allow different processors handle that structure for things like validation, generate a symfony config tree, building valid json schema, etc etc.
Install with composer at krak/schema
<?php
use function Krak\Schema\{struct, listOf, dict, string, bool, int};
$schema = struct([
'name' => string(),
'isAdmin' => bool(),
'age' => int(),
'tags' => listOf(string()),
'photos' => dict(struct([
'url' => string(),
'width' => int(),
'height' => int(),
]))
]);
/* would match a structure like:
{
"name": "Bob",
"isAdmin": true,
"age": 26,
"tags": ["tall", "dark", "handsome"],
"photos": {
"small": {
"url": "https://mydomain.com/images/bob/small",
"width": 100,
"height": 200
},
"large": {
"url": "https://mydomain.com/images/bob/large",
"width": 600,
"height": 1200
},
}
}
*/
Eventually we'll support the ability to take a schema and validate array structures against them.
Declare and build symfony config tree builders declaratively with the configTree
schema processor.
<?php
use Symfony\Component\Config\Definition\{ConfigurationInterface, TreeBuilder};
use function Krak\Schema\ProcessSchema\SymfonyConfig\configTree;
use function Krak\Schema\{struct, string};
final class Configuration implements ConfigurationInterface
{
public function getConfigTreeBuilder() {
return configTree('aws', struct([
'version' => string(),
'region' => string(),
'credentials' => struct([
'key' => string(),
'secret' => string(),
])
]));
}
}
Note: This currently supports Symfony 4 and 5 config.
Check out the feature test suite to see examples of all the supported api.
Here's a seemingly simple config file that we'd want to validate the schema of:
my_package:
string_key: 'abc'
int_key: 1
struct_key:
a: 1
b: 2
list_key: [1, 2, 3]
list_of_struct_key:
- a: 1
b: 2
struct_of_list:
a: ['', '']
b: [0, 0]
Here is the builder syntax:
return (new TreeBuilder('my_package'))->getRootNode();
->children()
->scalarNode('string_key')->end()
->integerNode('int_key')->end()
->arrayNode('struct_key')
->children()
->scalarNode('a')->end()
->integerNode('b')->end()
->end()
->end()
->arrayNode('list_key')
->integerPrototype()->end()
->end()
->arrayNode('list_of_struct_key')
->arrayPrototype()
->children()
->integerNode('a')->end()
->integerNode('b')->end()
->end()
->end()
->end()
->arrayNode('struct_of_list_key')
->children()
->arrayNode('a')
->scalarPrototype()->end()
->end()
->arrayNode('b')
->integerPrototype()->end()
->end()
->end()
->end()
->end()
->end();
Here is the declarative syntax for the same definition:
return configTree('my_package', struct([
'string_key' => string(),
'int_key' => int(),
'struct_key' => struct([
'a' => int(),
'b' => int(),
]),
'list_key' => listOf(int()),
'list_of_struct_key' => listOf(struct([
'a' => int(),
'b' => int(),
])),
'struct_of_list_key' => struct([
'a' => listOf(string()),
'b' => listOf(int()),
])
]));
Original RFC Pull Request to Symfony: symfony/symfony#35127
No formal API documentation is setup, but the src dir is under 200loc at this point. Also the tests directory gives a good overview of the various features as well.
Run composer test
to run the test suite.
- Api Documentation
- Additional schema fns to support more string/numeric constraints (regex, min, max, etc)
- JSON Schema ProcessSchema
- Create the ability to export a schema definition to valid json schema json
- Validation ProcessSchema
- Create a function validation library for basic schemas
- Support custom validators and schema fns
- Symfony Validation ProcessSchema
- Export to symfony constraints to use with the SF validator. With one api, we could define schemas that export to SF config and SF validation!