We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
f6b1886
This commit changed the way guards work. Now they can only stop a transition, but can't explicitly approve it like before. This is a huge BC break.
Previously if a guard returned true, the transition was good to go. Now it has to pass the regular checks too, and those will most likely fail.
There might be nothing to do about this now, but these changes should result in a major version bump in the future.
The text was updated successfully, but these errors were encountered:
#107
Sorry, something went wrong.
BC StateMachine for anyone looking
parameters: finite.state_machine.class: AppBundle\Finite\StateMachine
class StateMachine extends \Finite\StateMachine\StateMachine { /** * {@inheritdoc} */ public function can($transition, array $parameters = []) { $transition = $transition instanceof TransitionInterface ? $transition : $this->getTransition($transition); if ($transition->getGuard()) { return call_user_func($transition->getGuard(), $this); } return parent::can($transition, $parameters); } }
No branches or pull requests
f6b1886
This commit changed the way guards work. Now they can only stop a transition, but can't explicitly approve it like before. This is a huge BC break.
Previously if a guard returned true, the transition was good to go. Now it has to pass the regular checks too, and those will most likely fail.
There might be nothing to do about this now, but these changes should result in a major version bump in the future.
The text was updated successfully, but these errors were encountered: