Use Route ID Instead of Name

[reergymerej]

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.

[davidLeonardi]

Feel free to make a PR :)

On Thu, Mar 3, 2016 at 3:30 PM Jeremy Greer notifications@github.com
wrote:

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
.

[reergymerej]

@SEthX done and done!

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.

[davidLeonardi]

Please refer to discussion ongoing in #91

[charpeni]

PR #91 was merged, I'll close thank you @reergymerej.