Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposal: Routing Guide (Work In Progress) #122
tldr; We propose a guide that teaches how to setup
The following lists different problems we would like to see addressed:
Please let us know in the comments below which are most important to you or others you would like to see.
Values with delimiters (ex:
referenced this issue
Nov 3, 2017
Is there a recommended way to implement a back button?
Does history.back() work? https://developer.mozilla.org/en-US/docs/Web/API/Window/history
When I use update() with two variables, I expect #!/page/section but I get #!page/section. How do I add a slash in there?
Can you provide an example?
The if/else logic tree that is in bitcentive
What kind of bugs are you having?
So the thing to know about CanJS's routing is that it's usually like:
The URL gets translated to some stateful representation. Then, the
We might be able to make this a bit more declaratively, or w/ something like Streamy VMs make it a bit easier to test. But I'm not sure this logic can go away and still maintain the
One idea might be to have a convention like:
But it still would be tricky in include the session in this convention.
Is there a good way to test can-route?
I show some up above. Thoughts about those?
Update route with state from outside the route.
I'm not sure how to summarize this, but @mjstahl was trying to keep the URL consistent with what page the user was on given their session state.
For example, if a user went to