Route id

[xarvic]

Adds Notification::route

[maan2003]

so route only has id of the immediate child, not the full route. can you explain the usecase and how this will help? Also why not use Vec<WidgetId> for the widgets it traveled

[xarvic]

so route only has id of the immediate child, not the full route. can you explain the usecase and how this will help? Also why not use Vec for the widgets it traveled

The immediate child ID is useful, since it is easily accessible from the current widget.
For an example, if we want to implement the correct scroll_to behavior for enum_switcher, we need to know whether the notification came from within the active widget, if not we should discard it.
In the linked issue are more examples.

[maan2003]

Thanks! makes sense.

It is nice to update the notifications test but not a blocker.