securityService injected in home controller, but missing.

[talss89]

The title says it all really.

Rather than remove the dependency on securityService, I think it would make sense to provide a skeleton securityService instance. One that simply returns authorised and "Guest" as username.

It seems to me that securityService is a useful design pattern to keep as a template.

I'm using this code currently:

define(['./module'], function (services) {
    'use strict';

    services.service('securityService', ['$q', function($q)  {

        this.hasValidToken = function() {

           return $q.when(true);
        };

        this.getUserInfos = function() {
            return $q.when({name: "Guest"});
        };

    }]);
});

[talss89]

The home view attempts to display $scope.username on the footer navbar.

My code above will return an object, and the home controller is storing the return value of securityService.getUserInfos() in $scope.user

I've updated the view on my fork so we're displaying $scope.user.name

[jgrenon]

Yes, I removed it before publishing the project. My plan was to make a new version of the whole thing, but didn't have the time. Can you create a pull request with your code? I'll add it to the project as the default SecurityService.

[talss89]

Cool, I'll do this now.

I'll include the minor change to views/home.jade in the pull request too.