Skip to content

Conversation

@franzliedke
Copy link
Contributor

Because of #25497 and #25512, all facades in core are now properly
using service identifiers (strings) for resolving their "root"
service from the container. This means that the hack for resolving
objects directly can now be removed.

In case you're wondering why this is necessary: As far as I can
tell, facade features like ::swap() did not work with these types
of facades (Blade and Schema), because those methods did not deal
with the possibility of objects being returned.

Because of laravel#25497 and laravel#25512, all facades in core are now properly
using service identifiers (strings) for resolving their "root"
service from the container. This means that the hack for resolving
objects directly can now be removed.

In case you're wondering why this is necessary: As far as I can
tell, facade features like ::swap() did not work with these types
of facades (Blade and Schema), because those methods did not deal
with the possibility of objects being returned.
@franzliedke
Copy link
Contributor Author

@tillkruss This would probably need a note in the changelog, to warn package developers who wrote their own facades. Not sure what the right procedure is in this regard, so I am tagging you. 🙈

@tillkruss
Copy link
Contributor

Ping @themsaid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants