Closed jchesne closed 6 years ago
@jchesne thanks for your suggestion. However, we don't have plans to add this feature soon. In any case, I've added it to our public roadmap for future consideration. See https://github.com/javiereguiluz/EasyAdminBundle/projects/1#card-6420581
Coming from a real-world db dev background I would like to add that this feature is not something that should be missing in any serious app. It is a very basic requirement that you look for when checking frameworks for "real world enterprise features". It is quite disturbing to read that statement from a symfony core developer - I expected something like this comes oob, instead I see that you do not want to integrate it... why?
Please do not misunderstand me, I am not trying to attack you here, but I want to understand why such a basic and important functionality is considered not important in the symfony community. Thanks!
Also: How would you suggest people add this feature to their code? Just falling back to the doctrine "version" tag and handling the resulting exception manually everywhere? Really?
@symfonysos If it's so basic, you can always just implement it and share with everyone :).
It would be fantastic to be able to lock content as SonataAdmin does (https://symfony.com/doc/master/bundles/SonataAdminBundle/cookbook/recipe_lock_protection.html)
When we work at multipes admin on the same content, a lock can prevent others to override already submited datas.