- Issue created by @jsacksick
- Status changed to Needs review
over 1 year ago 4:21pm 23 February 2023 - 🇮🇱Israel jsacksick
Let's see if some tests are failing, but the logic in the attached patch makes way more sense to me than the current one, considering we aren't blindly testing all the transitions.
This won't solve my other issues as I realized that we're checking the allowed transitions in several places, and not just when we're about to apply them...
- 🇮🇱Israel jsacksick
Minor change (we already return early if the workflow isn't known).
The last submitted patch, 3: 3344049-3.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.The last submitted patch, 5: 3344049-4.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- Status changed to Fixed
over 1 year ago 7:52am 24 February 2023 -
jsacksick →
committed d8a94838 on 8.x-1.x
Issue #3344049 by jsacksick: State transition validation should only...
-
jsacksick →
committed d8a94838 on 8.x-1.x
- 🇮🇱Israel jsacksick
I'm having second thoughts on the
isTransitionAllowed()
method that was made public on the Workflow.The problem is that it doesn't check if the transition is possible. So either we need to document this, or mark it as protected again, which means we wouldn't be able to solve this...
Automatically closed - issue fixed for 2 weeks with no activity.