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
{{ message }}
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
In the same vain, having "sign in" and "sign up" directives could be useful to easily move this forms in another place (for instance, on the landing page).
For anyone interested, I have a generated project in a test repo that contains an opinionated 'angular-fullstack navbar'.
Opinions:
move as much manipulation logic out of the controller as possible
store navbar data in a service so it can be accessed by other controllers, services, etc...
use the controllerAs syntax
bind Auth to the $scope, not the Controller(this)
Also, I took a first attempt at writing test. I included a spec for the controller, service, and directive. Being those are my first 'test' with karma or jasmine, I wouldn't mind if someone pointed out any mistakes or shortcomings.
More specifically, it's because the socket.io endpoint has been changed and you client was 'polling' the old endpoint. Which would now simply default to serving the main index.html; hence all the the short 200 responses.
Activity
remicastaing commentedon Aug 17, 2014
In the same vain, having "sign in" and "sign up" directives could be useful to easily move this forms in another place (for instance, on the landing page).
kingcody commentedon Aug 17, 2014
Or in a modal :)
kingcody commentedon Aug 17, 2014
For anyone interested, I have a generated project in a test repo that contains an opinionated 'angular-fullstack navbar'.
Opinions:
serviceso it can be accessed by other controllers, services, etc...Authto the $scope, not the Controller(this)Also, I took a first attempt at writing test. I included a spec for the controller, service, and directive. Being those are my first 'test' with karma or jasmine, I wouldn't mind if someone pointed out any mistakes or shortcomings.
remicastaing commentedon Aug 17, 2014
How can I get rid of all this request:
It's polluting the console.
remicastaing commentedon Aug 17, 2014
Weird. They are gone.
kingcody commentedon Aug 17, 2014
It's from restarting the server and not doing a fresh reload on the client side.
A 'force reload' in the browser always fixes it for me.
kingcody commentedon Aug 17, 2014
More specifically, it's because the socket.io endpoint has been changed and you client was 'polling' the old endpoint. Which would now simply default to serving the main index.html; hence all the the short
200responses.