search

symfony2admingenerator / GeneratorBundle

Admingenerator for Symfony. Parse YAML files to build customized backend.
MIT License
67 stars 29 forks source link

[RFC] Implement Symfony3.2 workflow component #296

Open ioleo opened 8 years ago

ioleo commented 8 years ago

It seems like symfony 3.2 workflow component could be a perfect addition to admingenerator. We should think how it could be easily implemented into out tempaltes without breaking current behaviour. Or maybe it's worth a BC break? Please share your thoughts.

javiereguiluz commented 8 years ago

I'd like to ask you in which kind of operations/tasks are you thinking about integrating the new Workflow component. Thanks!

bobvandevijver commented 8 years ago

For reference: the Symfony 3.2 Workflow component

I'm also not sure where we would want to use it. You want to add the workflow to the editing of the bundle? I'm not sure if that's something we would want, imho it is out of the scope of this bundle.

ioleo commented 8 years ago

I meant adding support workflow_can checks instead/in addition to(?) of security is_granted checks.

bobvandevijver commented 8 years ago

That's is not where the workflow component is meant to be used for if I understand it correctly. How does a state change if you want to view the list? Or if you simply only edit the object?

I would stay with the is_granted-checks.

ioleo commented 8 years ago

True :) the view / list actions require simple credential checks, but for custom object actions (which in my projects are mostly state transitions like accept, send, publish etc) it could be useful to use the workflow component