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
[Workflow] buildTransitionBlockerList contains meaningles if block #28429
Comments
I think that's just some bad copy and paste when the feature was implemented. Would you like to send a PR changing it? |
I'm not sure how exactly workflow works. There are multiple possible fixes depending on how many same name transitions are allowed. |
Hello, indeed this is a typo But the fix is not trivial because the code have to make a decision based on a subjective decision. |
…ny transition are enabled (Tetragramat, lyrixx) This PR was merged into the 4.1 branch. Discussion ---------- [Workflow] Fixed bug of buildTransitionBlockerList when many transition are enabled | Q | A | ------------- | --- | Branch? | 4.1 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #28429 #28432 #28493 | License | MIT | Doc PR | <!-- Write a short README entry for your feature/bugfix here (replace this comment block.) This will help people understand your PR and can be used as a start of the Doc PR. Additionally: - Bug fixes must be submitted against the lowest branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the master branch. --> Commits ------- 732f343 [Workflow] Made code simpler db69ccc method buildTransitionBlockerList returns TransitionBlockerList of expected transition
Symfony version(s) affected: 4.1.4
Description
This line does not make any sense. https://github.com/symfony/symfony/blob/v4.1.4/src/Symfony/Component/Workflow/Workflow.php#L122
Possible Solution
Replace continue with break and negate condition or remove if block completelly.
The text was updated successfully, but these errors were encountered: