search

kadirahq / flow-router

Carefully Designed Client Side Router for Meteor
MIT License
1.09k stars 195 forks source link

getRouteName() is no longer reactive after visit an incorrect route #716

Closed ghost closed 7 years ago

ghost commented 7 years ago

The issue is simple. When you visit a route who not exists, the function FlowRouter.getRouterName() is no longer reactive. The function works always, but the reactive capability is lost.

ghost commented 7 years ago

Hum... After verification, there is no issue, in fact... Sorry :)