Small refactorings as a follow-up to iterable trigger
What does this MR do and why?
Small refactorings as a follow-up to iterable trigger
- follow-ups from #417645 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #417645 (closed)
Edited by Doug Stull