Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Implement Symfony3.2 workflow component #296

Open
ioleo opened this issue Jul 22, 2016 · 5 comments
Open

[RFC] Implement Symfony3.2 workflow component #296

ioleo opened this issue Jul 22, 2016 · 5 comments

Comments

@ioleo
Copy link
Member

ioleo commented Jul 22, 2016

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
Copy link

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

@bobvandevijver
Copy link
Member

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
Copy link
Member Author

ioleo commented Jul 22, 2016

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

@bobvandevijver
Copy link
Member

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
Copy link
Member Author

ioleo commented Jul 22, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants