See attached screenshot: We would like to re-use the checkout step as defined in the parent configuration, but extend it in OO style to additionally execute the checkout-qb-native... step.
This would increase maintainability if e.g. the checkout step (as defined in the parent configuration) is modified. For now we can of course use a workaround using some duplication...
If avoiding circular dependencies is by default mostly desirable, this new feature could be optional, e.g. by guarding by a flag or so.
Description
See attached screenshot: We would like to re-use the checkout step as defined in the parent configuration, but extend it in OO style to additionally execute the checkout-qb-native... step.
This would increase maintainability if e.g. the checkout step (as defined in the parent configuration) is modified. For now we can of course use a workaround using some duplication...
If avoiding circular dependencies is by default mostly desirable, this new feature could be optional, e.g. by guarding by a flag or so.
Improvement
Open
Major
Overriding a step should allow to select overridden step as child step too (cf. super keyword in Java) instead of detecting the circular reference
