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

Permit spinner to function without nested routes (ie. at base route level) #2

Open
rpocklin opened this issue Aug 23, 2015 · 0 comments

Comments

@rpocklin
Copy link
Owner

Currently the design works for routes with a common parent. Ideally it should work even when the root state is empty. This may involve re-writing portions of the code or determining if this is the first time a view is loaded in the app (ie. initial bootstrapping of angular).

Ie. switching between /account and /settings should be able to show a spinner which is part of the initial ng-view.

Possibly relates to Issue #1

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

No branches or pull requests

1 participant