Zack Teska

Hi, sorry for the radio silence on this one. At first glance, this might be because from a null state, the initial state is "entered" first, and that does fire...

Yeah, the array syntax isn't great for this since it's only an approximation of the way Symfony handles it. Happy to consider a PR for this, but I think we...

I must be missing something in what you're saying. The docs clearly show multiple places using the same transition via "OR": https://symfony.com/doc/current/workflow/workflow-and-state-machine.html#state-machines It's something the code-side of the component fully...

> * Remove the option to use array keys as transition name and enforce `name` attribute, it is already present in your service provider but is optional; As this is...

@klimenttoshkov Sure! I'd be happy to! You can DM me on twitter `@zero_dahero` and we can exchange contact info and get something set up!

Oh, that must explain why I'm not more popular on twitter 🤣 Try now, I think I enabled that.

Looks like we're going to need to do some work to support Symfony 7 (and clear up these warnings in the meantime). A quick glance at the code suggests the...

Fixed with v5: https://github.com/zerodahero/laravel-workflow/releases/tag/v5.0.0

Released with v5: https://github.com/zerodahero/laravel-workflow/releases/tag/v5.0.0

I'm currently maintaining a fork of this at https://github.com/zerodahero/laravel-workflow (it's on packagist, too) which supports Laravel 7. It contains a few extra features that were necessary for my purposes, but...