You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to use an ID instead of name to identify routes. In some cases, you'd want to use the same title for multiple routes. When observing the routeEmitter, you only get the name (aka user-friendly title), so you don't know which route was triggered.
For now, I'm using the titleComponent and titleProps to separate the name from visible title. It works, but it's extra cruft.
The text was updated successfully, but these errors were encountered:
It would be nice to use an ID instead of name to identify routes. In some
cases, you'd want to use the same title for multiple routes. When observing
the routeEmitter, you only get the name (aka user-friendly title), so you
don't know which route was triggered.
For now, I'm using the titleComponent and titleProps to separate the name
from visible title. It works, but it's extra cruft.
—
Reply to this email directly or view it on GitHub #90
.
I left it open and just included the route in addition to the route name. This way, existing code won't break and devs can query whatever they want instead of introducing an id requirement.
It would be nice to use an ID instead of name to identify routes. In some cases, you'd want to use the same title for multiple routes. When observing the
routeEmitter
, you only get the name (aka user-friendly title), so you don't know which route was triggered.For now, I'm using the
titleComponent
andtitleProps
to separate the name from visible title. It works, but it's extra cruft.The text was updated successfully, but these errors were encountered: