Skip to content

Conversation

@kbond
Copy link

@kbond kbond commented Nov 20, 2021

No description provided.

@weaverryan weaverryan merged commit d9c495d into weaverryan:symfony6-support Nov 20, 2021
@weaverryan
Copy link
Owner

Beautiful - thank you!

@kbond kbond deleted the test-container branch November 20, 2021 21:50
weaverryan added a commit that referenced this pull request Nov 1, 2022
# 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
weaverryan pushed a commit that referenced this pull request Apr 27, 2025
weaverryan pushed a commit that referenced this pull request Apr 27, 2025
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
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.

2 participants