Is it intentional that facade and helper function differ in triggering beforeResolving event?

[nanaya]

Given this in app service provider's register:

$this->app->beforeResolving(function () {
  echo 'before resolving something'.PHP_EOL;
});

I'm getting different results between using app('session')/session() helpers and Session facade:

> Session::get('x')
before resolving something
before resolving something
before resolving something
= null

> app('session')->get('x')
before resolving something
= null

> session()->get('x')
before resolving something
= null

> Session::get('x')
= null

> session()->get('x')
before resolving something
= null

Is this intentional that facade only triggers the event on first usage? (or that app resolver triggers the event every time for singleton)

[crynobone]

All facades behaves like a singleton and will only resolved once during the request.

[nanaya]

so it's intentional that using app() or helper functions (session(), auth(), etc) triggers beforeResolving event while facade (Session, Auth) doesn't?

[crynobone]

That's not correct. Helpers and Facades will get resolved through the IoC, If the binding is Singleton, then it will resolved once per request otherwise it will resolved each time you call it. Facade at the same time, cached the resolved instance and that make it behave as a singleton. Your example above prove this behavior

[nanaya]

I've been talking in context of second and later calls to the corresponding functions/facades in same request...

In term of code, this:

session()->get('x');
session()->get('x');

Triggers beforeResolving for 'session' twice.

Whereas this:

Session::get('x');
Session::get('x');

Only triggers beforeResolving for 'session' once.

So this is correct and intentional, right?

[crynobone]

Yes, that's correct.