Eric Burel

Ok I'll try to merge it within a few days

@EloyID #2552 is now merged into devel. I've also pushed the commit on "feature/datatable" (I had forgotten to push sorry)

Awesome work! We will test that alongside #2497

Hi, according to @yannick-mayeur tests it does not seem to correctly add data in lists on item creation, any idea why? Edit: actually we can't test this correctly yet because...

You might want to check this: https://github.com/VulcanJS/vulcan-next/issues/9 More broadly it would be awesome to have a standard for Vulcan packages, settings one of the field.

Thanks for pointing that out. Will add it whenever we have a chance to rework on schema nesting.

Note that it's still in beta, in my other app I have issues with SSR currrently so we must be careful. I prefer to do such update a bit later...

It shouldn't be too hard (everything happens in `schemaFields.js`, it's just new case) but I have questions about mutations, forms, and default fragments. We can't have union inputs so right...

We don't necessarily have to wait, we may figure alternative. For example using a `JSON` for the input type could be sufficient already. It's ok if we lose graphQL validation...

Thanks! It will break existing applications yes, I've slightly updated the migrating doc and Sacha had published articles about the new API on vulcan blog. But this PR specifically is...