Closed Gabeblis closed 21 hours ago
@Gabeblis you know the fix and got something in mind? I just tested this behavior and it works the same for me. Moving to from Backlog to Ready.
@Gabeblis you know the fix and got something in mind? I just tested this behavior and it works the same for me. Moving to from Backlog to Ready.
Yes, I have a fix in mind. We can use a bit of regex to clean up each line for an exact comparison, rather than using the includes
method. This way, we ensure that only the exact constraint is matched and run, without including similar strings. It's a tiny change. I can open a PR for this when there is room.
This relates to ...
What happened?
When running the constraint script,
(npm run constraint <constraint-id>)
, it runs more than one constraint. I noticed that this behavior happens when another constraint id ends with the constraint id that you are running.Relevant log output
How do we replicate this issue?
Run
npm run constraint cloud-service-model
and then it will run that constraint and alsohas-cloud-service-model
.Where, exactly?
This occurs in the
constraint
script. Specifically, the cause is indev-constraint.js
under scripts in thedevelop
branch.Other relevant details
No response