Ghost/ghost/admin/tests/unit
Kevin Ansfield c646e78fff Made session.user a synchronous property rather than a promise
no issue

Having `session.user` return a promise made dealing with it in components difficult because you always had to remember it returned a promise rather than a model and had to handle the async behaviour. It also meant that you couldn't use any current user properties directly inside getters which made refactors to Glimmer/Octane idioms harder to reason about.

`session.user` was a cached computed property so it really made no sense for it to be a promise - it was loaded on first access and then always returned instantly but with a fulfilled promise rather than the  underlying model.

Refactoring to a synchronous property that is loaded as part of the authentication flows (we load the current user to check that we're logged in - we may as well make use of that!) means one less thing to be aware of/remember and provides a nicer migration process to Glimmer components. As part of the refactor, the auth flows and pre-load of required data across other services was also simplified to make it easier to find and follow.

- refactored app setup and `session.user`
  - added `session.populateUser()` that fetches a user model from the current user endpoint and sets it on `session.user`
  - removed knowledge of app setup from the `cookie` authenticator and moved it into = `session.postAuthPreparation()`, this means we have the same post-authentication setup no matter which authenticator is used so we have more consistent behaviour in tests which don't use the `cookie` authenticator
  - switched `session` service to native class syntax to get the expected `super()` behaviour
  - updated `handleAuthentication()` so it populate's `session.user` and performs post-auth setup before transitioning (handles sign-in after app load)
  - updated `application` route to remove duplicated knowledge of app preload behaviour that now lives in `session.postAuthPreparation()` (handles already-authed app load)
  - removed out-of-date attempt at pre-loading data from setup controller as that's now handled automatically via `session.handleAuthentication`
- updated app code to not treat `session.user` as a promise
  - predominant usage was router `beforeModel` hooks that transitioned users without valid permissions, this sets us up for an easier removal of the `current-user-settings` mixin in the future
2021-07-08 14:54:31 +01:00
..
authenticators Made session.user a synchronous property rather than a promise 2021-07-08 14:54:31 +01:00
components Update dependency ember-mocha to v0.16.0 2019-06-17 15:32:09 +01:00
controllers Fixed tests 2021-06-21 15:18:11 +01:00
helpers Updated character counter color 2021-07-08 15:15:49 +02:00
mixins Update dependency eslint-plugin-ghost to v1.4.0 2020-05-06 18:07:01 +01:00
models 🐛 Fixed host limit error when resending a pending invite (#1881) 2021-04-06 15:10:03 +12:00
serializers Switched from v3 to canary API 2021-02-05 09:12:26 +00:00
services Added integration with limit service 2021-04-08 16:59:56 +12:00
transforms Fixed EmberObject.create error on Admin start (#1841) 2021-02-18 13:25:21 +13:00
utils Migrate to latest ember, ember-mocha and modern ember testing (#1044) 2019-01-02 09:58:55 +00:00
validators 🔥 Removed all subscriber feature related code (#1337) 2019-09-26 15:58:01 +02:00
.gitkeep Ember init, bower deps, es6 modules 2015-03-11 12:37:41 -06:00