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
Any reason to enforce location: hash vs none as part of the Ember framework validations?
Let's just say in our experiments w stacked native routing, we ended up disabling URL changes entirely, and while it's not big hassle to re-enable hash routing, seems like we should just be able to leave it off, no?
The text was updated successfully, but these errors were encountered:
Any reason to enforce location:
hash
vsnone
as part of the Ember framework validations?Let's just say in our experiments w stacked native routing, we ended up disabling URL changes entirely, and while it's not big hassle to re-enable hash routing, seems like we should just be able to leave it off, no?
The text was updated successfully, but these errors were encountered: