Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to using html5 routes #15

Closed
pkozlowski-opensource opened this issue Sep 22, 2012 · 4 comments
Closed

Switch to using html5 routes #15

pkozlowski-opensource opened this issue Sep 22, 2012 · 4 comments

Comments

@pkozlowski-opensource
Copy link
Member

Depends on #14.

We might need to add a $navigation service (name to be decided) that would allow us to remove paths as strings from both templates and controllers.

@ghost ghost assigned petebacondarwin Sep 22, 2012
@petebacondarwin
Copy link
Contributor

Yes this becomes more important if we want to move to html5mode.

Pete
...from my mobile.
On Sep 22, 2012 9:35 AM, "Pawel Kozlowski" notifications@github.com wrote:

Depends on #14 #14.

We might need to add a $navigation service (name to be decided) that would
allow us to remove paths as strings from both templates and controllers.


Reply to this email directly or view it on GitHubhttps://github.com//issues/15.

@petebacondarwin
Copy link
Contributor

The backend server now supports HTML5 routes. Just a case of updating the app. Now how are we going to manage that? Just a straight change of all the URLs or something more clever?

@pkozlowski-opensource
Copy link
Member Author

We've got another ticket to introduce the $navigation service but we
might do it in this one as well.

@pkozlowski-opensource
Copy link
Member Author

Done in d4664be. Still we need further work on a navigation service (#21).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants