Ryan Tablada

@driesvints I am also having this issue with a fresh L5 and Lock installation...

@driesvints I'm not sure if this is the issue that @lbausch is having but I found that my issue was that I was resetting the Auth::user in my OAuth middleware....

It's ugly, but this is our middleware right now: ``` php public function handle($request, Closure $next) { $this->filter(); $userId = $this->authorizer->getChecker()->getAccessToken()->getSession()->getOwnerId(); try { Auth::onceUsingId($userId); $user = Auth::user(); $manager = app('lock.manager');...

I think removing `ember-moment-shims` would be 👍 for me. The new import support for Ember CLI would mean that users may start using non-shimmed moment soon (we're looking at it...

@cibernox I think a step toward this would be to use a blueprint to install `ember-moment` in the host app. Right now I was really excited to think we had...

So actionable steps could be: 1. Move `ember-moment` to blueprint install (and remove `ember-moment` and `ember-moment-shims` from `dependencies`) 2. Start removing references to helpers provided by `ember-moment` (still relying on...

I'm not sure how simple abstracting moment/luxon will be since they have different API surfaces (and the abstraction would likely be fairly large in size). My goal isn't to limit...

Any update on this? we have a lot of stuff and there's a lot of classic decorator annotations that aren't really needed with no way to prevent them.

Using overlay position does prevent the closing (depending on some CSS hierarchy) though it seems like there should be a better native event listener to make sure that this is...

We actually had this come up. I accidentally use this as a behavior to refresh a route without realizing this was going on until I called it twice... 🤦🏽 This...