Where to load common data in an application with authentication

Question

I have an application with a sidebar which is always visible. For this sidebar I have to load common data once. This is usually not a problem, I do this in the setupController hook of the ApplicationRoute.

Tedian.ApplicationRoute = Ember.Route.extend
  setupController: ->
    controller = @controllerFor("sidebar")
    controller.set "tasks", @store.find("task")
    controller.set "projects", @store.find("project")
    controller.set "timeEntries", @store.find("timeEntry")

    Tedian.TimeEntry.findActive().then (timeEntry) ->
      controller.set "activeTimeEntry", timeEntry

But where do I put this setup code in an application with authentication?

I don't want to run this code for an un-authenticated user so I can't put it into the ApplicationRoute. Where is the best place to put it instead?

How do you will do the authentication logic? Using some framework or by hand etc. — Marcio Junior
– Marcio Junior, Commented Nov 21, 2013 at 15:03
I'm doing it by hand, similar to this: log.simplabs.com/post/53016599611/authentication-in-ember-js — stravid
– stravid, Commented Nov 21, 2013 at 15:19
it would go in App.SessionsNewRoute createSession action then. — Michael Johnston
– Michael Johnston, Commented Nov 21, 2013 at 16:56

Eaten by a grue · Accepted Answer · 2013-11-25 10:25:48Z

1

Perhaps i'm too stupid here, but i would simply check if the user is logged in:

App.ApplicationRoute = Ember.Route.extend({

   initializeSidebar: function() {
      if (!App.user.get('isSignedIn')) return;
      var controller = this.controllerFor('sidebar');
      //...
   }.observes('App.user.isSignedIn'),

   setupController: function(controller, model) {
       controller.set('model', model);
       this.initializeSidebar();
   }
});

Now, if the user signs in or the user is already signed in, but the information about that comes asynchronously, the sidebar gets updated.

I don't know if it's a good practice to store the user object directly on the App, but as you want access it from everywhere anyways, i think it's ok. Alternatively have it as an attribute of a controller that you then can access from the ApplicationRoute by calling this.controllerFor('')

edited Nov 25, 2013 at 10:25

answered Nov 22, 2013 at 20:22

Eaten by a grue

3912 silver badges5 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

stravid Over a year ago

I did something very similar where my login controller would dispatch an event which is catched at the ApplicationRoute. Thanks!

Toran Billups · Accepted Answer · 2013-11-21 15:09:19Z

0

You could check to see if the user is authenticated when the app boots

App.initializer({
  name: 'bootstrap',
  initialize: function() {
    //if user is authenticated do a $.ajax or 2 in here
  }
});

answered Nov 21, 2013 at 15:09

Toran Billups

27.4k41 gold badges159 silver badges272 bronze badges

2 Comments

stravid Over a year ago

What happens when I'm not authenticated when the app boots but I sign in after that? A sign in doesn't cause an page load so the boot logic already happened.

Toran Billups Over a year ago

ah yes - this would require another type of action driven by another component

Dave-Choi · Accepted Answer · 2013-11-21 21:59:31Z

Most likely, you'll want to have a User model that has several hasMany relationships with your Task, Project and TimeEntry models. Then, when you authenticate your user, however you do that, the server response should include those related models.

Then your SidebarController can have a controller need for the current user:

App.SidebarController = Ember.Controller.extend({
    needs: ["currentUser"]
});

And your sidebar template can have something like

{{render "tasks" currentUser.tasks}}
{{render "projects" currentUser.projects}}
{{render "timeEntries" currentUser.timeEntries}}

And those will populate automatically when you set the currentUser with the appropriate data.

If you don't have control over the server response, then you can have an observer on the currentUserController fetch that stuff after authentication.

Collectives™ on Stack Overflow

Where to load common data in an application with authentication

3 Answers 3

1 Comment

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related