Draft: Switch to use a more familiar reliance on params on subscriptions
What does this MR do and why?
Switch to use a more familiar reliance on params on subscriptions
- move away from route comparison logic from using stored return to logic as that can muddy things and be fragile
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #418820 (closed)