Roger Saner

The current state is a string, so if you can save the string to your database, then when you set up your state machine you first load up the value...

@jkufner I wrap the state machine transition in a service, and call the service to do the transition. If the transition succeeds, then I update the database by calling `$myEntity->setState()`....

@jkufner not quite. `Finite` provides a state machine but doesn't provide any implementation of persisting to the database - that's left to the developer to implement. When instantiating the state...

This is great, and should be the default behaviour of `AssociationField` when it's a `ToMany` relationship, as was the behaviour in version 2.0. Instead, the 3.0 behaviour is to just...

I've adjusted your twig template slightly, because if an entity does not have a CRUD controller created for it, I get this error: `Argument 1 passed to EasyCorp\Bundle\EasyAdminBundle\Registry\CrudControllerRegistry::findCrudIdByCrudFqcn() must be...

An update to `templates/bundles/EasyAdminBundle/default/field_multiple_association.html.twig` incorporating the changes from https://github.com/EasyCorp/EasyAdminBundle/issues/3774#issuecomment-697196605 ```twig {# @var ea \EasyCorp\Bundle\EasyAdminBundle\Context\AdminContext #} {# @var field \EasyCorp\Bundle\EasyAdminBundle\Dto\FieldDto #} {# @var entity \EasyCorp\Bundle\EasyAdminBundle\Dto\EntityDto #} {# To be replaced by...

The solution at https://github.com/EasyCorp/EasyAdminBundle/issues/3349#issuecomment-695214741 works nicely, however, it doesn't allow EasyAdmin to expose any other fields on the User entity. I don't see a way to do that by changing...

I have the same issue, but solved it by removing `node_modules` and re-installed using `yarn` instead of `npm`. Somehow that worked! ### Background When running `npm run dev` on a...

Are you including `resource_shop_list.js` in any of your other javascript files, especially `app.js`?

Thanks @quentint the gist works as I'd expect it to. To answer @javiereguiluz's question above: > Instead of creating a new EnumField, could we improve ChoiceField to allow passing a...