How can I restart subroutes? about backbone.subroute

[geekdave]

If I understand correctly, your issue is not with code inside backbone-subroute, itself... but rather with the the above code snippet that instantiates subroutes.

Specifically, it sounds like your route ":appName/*navPath": "loadApp" stops working for already-visited routes. Actually it's probably not the case that it stopped working... but it's just that a more specific route was created by your subrouter and backbone is matching that route instead of this base one.

So is it possible to remove all the subroutes that have already been initialized? This is a core Backbone Router question, and it's already been decided here. The answer is no. Jeremy Ashkenas said:

You should never be "removing" a route. URLs are supposed to be permanent. If you mint it, you keep it.

So I think this needs to be resolved in your application code, given the above assumptions about routes being permanent. Perhaps instead of enforcing the hasPermissions check at subroute instantiation time, it should be done at the time when a particular base view is created? This way, you would also have the advantage of being able to provide a descriptive "Access Denied" message in the UI instead of just silently ignoring the route (like your code seems to do now).

[patrixd]

Thank you for your help. Your idea is great. I allways go to a method
related with de module or subroute, where I could check the permissions. I
sometimes chek pemissions of specified views. With the check of the
subroute where I did it, avoids to me check again and again the
permissions. But when I needed to change initial configuration and
permission I got in that trouble.

Kind regards

El 05/07/2013, a las 22:27, Dave Cadwallader [email protected]
escribió:

If I understand correctly, your issue is not with code inside
backbone-subroute, itself... but rather with the the above code snippet
that instantiates subroutes.

Specifically, it sounds like your route ":appName/*navPath":
"loadApp"stops working for already-visited routes. Actually it's
probably not the
case that it stopped working... but it's just that a more specific route
was created by your subrouter and backbone is matching that route instead
of this base one.

So is it possible to remove all the subroutes that have already been
initialized? This is a core Backbone Router question, and it's already been
decided here jashkenas/backbone#1272. The
answer is no. Jeremy Ashkenas said:

You should never be "removing" a route. URLs are supposed to be permanent.
If you mint it, you keep it.

So I think this needs to be resolved in your application code, given the
above assumptions about routes being permanent. Perhaps instead of
enforcing the hasPermissions check at subroute instantiation time, it
should be done at the time when a particular base view is created? This
way, you would also have the advantage of being able to provide a
descriptive "Access Denied" message in the UI instead of just silently
ignoring the route (like your code seems to do now).

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/24#issuecomment-20537512
.