Philip

A new release would be great! Currently I'm depending on `"romaricdrigon/metayaml": "dev-master#1481b99679b29cbb50c88f3e10e4951ac64b8ad3",`. This works but raises a warning on Symfony Insight.

Hi, the idea of the required-flag is to reflect the NOT NULL constraint. It is called "required" due to the possibility to have non SQL-implementations. My practice is: required =...

Adding a flag to the field in the YAML is a good idea, I will do that. Right after the release of 0.14.0 which abstracts out the framework and then...

Mainly writing documentation is left. We are currently porting a bigger project to symfony4 and as soon as this works completly, I can be sure that the abstractions are fine.

# From https://github.com/philiplb/CRUDlex/issues/84: Hello, in my company I implemented an ad-hoc "Batch operations" feature, and I'm thinking about backporting it to crudlex In my case we wanted to delete all...

I just ran into this, too.

Any news about this?

Maybe it might be nice to not mangle the shader and it's metadata together and separate it? Like having a XML file with those attributes/parameters and the shader either within...

Just thinking as I type :) True that. I thought that you actually can write a whole specification with XML in some schema files etc.. External editors knowing the schema...

I was just typing that I'd find it strange as well to bind shaders to the project rather than to the application, but then this popped in: > It'd be...