This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
Remove angular-route in favor of a more adapted lightweight alternative #64
Milestone
Comments
|
Alternatively (in fact the complete opposite) we should think about making the flow stuff optional. This could be useful for apps that really consist of only one page, and apps already bringing their own tools for navigation. |
x1B
added a commit
that referenced
this issue
Jul 14, 2015
x1B
added a commit
that referenced
this issue
Jul 14, 2015
x1B
added a commit
that referenced
this issue
Jul 14, 2015
x1B
added a commit
that referenced
this issue
Jul 14, 2015
* feature/219-add-travis-ci: (#64) added Travis-CI build integration
|
I'll close this for now. With #267 we already switched to page.js. Adding the possibility of one-page single-page apps (:eyes:) should be tracked in a separate issue. Implemented on |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Most features of angular-route are not really used by LaxarJS (like
ngView) and instead the integration of the LaxarJS flow concept and pages makes some parts of the implementation more complicated and less straight forward than they need to be. Also #65.The text was updated successfully, but these errors were encountered: