-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ComponentBinder #470
Comments
The current implementation of PhpGt/ServiceContainer#140 means that any |
* build: upgrade dom requirement and loosen version range * docs: update examples * feature: trim whitespace when there are only template children closes #363 * maintenance: phpstorm analysis improvements * tweak: remove data-element attribute * feature: implement ComponentBinder and abstract Binder class for #470 * fix: bindable cache allows nested nullable objects closes #474 * refactor: all domtemplate classes set their dependencies outside of the constructor for #470 * tweak: stricter reflection type checking * wip: better exception on missing list element * tweak: handle nullable iterables closes #473 * tweak: handle binding of outer list item * tidy: improve types and coverage * ci: php 8.2 * ci: phpstan level 6
We already have the
DocumentBinder
. It would be useful to be able to bind to a specific Component.Following on from my thoughts on PhpGt/ServiceContainer#140, there should continue to be a
DocumentBinder
, but we should introduce aComponentBinder
that is pre-constrained to a Component, but we should also introduce aBinder
class that both DocumentBinder and ComponentBinder extend. This way, the developer could get into the habit of always requesting aBinder
, and only reach for the specific instance in the edge case where they need it.The text was updated successfully, but these errors were encountered: