-
Notifications
You must be signed in to change notification settings - Fork 569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route id #1978
Route id #1978
Conversation
Signed-off-by: Christoph <xarvix@web.de>
Signed-off-by: Christoph <xarvix@web.de>
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 |
Co-authored-by: Manmeet Maan <49202620+Maan2003@users.noreply.github.com>
The immediate child ID is useful, since it is easily accessible from the current widget. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! makes sense.
It is nice to update the notifications
test but not a blocker.
Adds
Notification::route