-
-
Notifications
You must be signed in to change notification settings - Fork 0
Add MountedComponent
object
#2
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
base: feature/twig-components-attributes
Are you sure you want to change the base?
Conversation
return $this->mounted->getMetadata(); | ||
} | ||
|
||
public function getMountedComponent(): MountedComponent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should drop getMetadata/getComponent and just have this method?
Alternatively, MountedComponent
is sort of an "internal" object so maybe we shouldn't include at all... We may want to keep it purely internal to allow us to make changes (add attributes via extension points) down the road.
The problem is, I need an instance of MountedComponent
in the AddLiveAttributesSubscriber
(to dehydrate the component) - this was the easiest way to provide.
# This is the 1st commit message: WIP heavy refactoring to Component Initial "hook" system used to reset model field after re-render Adding a 2nd hook to handle window unloaded reinit polling after re-render Adding Component proxy # This is the commit message #2: fixing some tests # This is the commit message #3: Refactoring loading to a hook # This is the commit message #4: fixing tests # This is the commit message #5: rearranging # This is the commit message #6: Refactoring polling to a separate class
This PR was merged into the 2.x branch. Discussion ---------- [LazyImage] Cache BlurHash, close #2 | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes <!-- please update src/**/CHANGELOG.md files --> | Issues | Fix #2 <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead --> | License | MIT <!-- Replace this notice by a description of your feature/bugfix. This will help reviewers and should be a good start for the documentation. Additionally (see https://symfony.com/releases): - Always add tests and ensure they pass. - For new features, provide some code snippets to help understand usage. - Features and deprecations must be submitted against branch main. - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry - Never break backward compatibility (see https://symfony.com/bc). --> Hi everyone, this PR is a proposal for #2, the second oldest issue on this repository 🤯 In some weeks at work we want to setup BlurHash images for performance reasons, caching them the first step! I've also though about decorates the `BlurHashInterface` if option `cache` is set, this way we don't modify the current `BlurHash`. Let me know what is preferred :) Commits ------- 21e3c43 [LazyImage] Cache BlurHash, close #2
Adds the
MountedComponent
object as a base for adding native attributes.