Skip to content

Draft: FPC support - #210

Open
toonvd wants to merge 285 commits into
magewirephp:mainfrom
toonvd:wire-cache
Open

Draft: FPC support#210
toonvd wants to merge 285 commits into
magewirephp:mainfrom
toonvd:wire-cache

Conversation

@toonvd

@toonvd toonvd commented Mar 27, 2026

Copy link
Copy Markdown

This PR stores HTML from successfull morphs in IndexedDB.
There are 2 possible versions of implementing this.

1: plain copying from IndexedDB on pageload and have a small diff between default value and whats in storage:
magewire_load_jump

2: hiding the element until the morph is done:
magewire_hide_element_until_load

Let me know what implementation you prefer. Also, my experience with Magewire is limited, please triplecheck for possible issues.

wpoortman and others added 30 commits November 23, 2021 13:03
* [feature/reset]:+ Component reset concept

* [develop]:+ Hide reset & fill methods for subsequent requests

* [feature/reset]:+ Reset takes into account reserved public properties

* [feature/reset]:+ Unset type on layout data if exists

* [feature/reset]:+ Reset docs
* [develop]:+ Ability to add layout handles on subsequent requests

* [develop]:+ Minor CA updates including a new 'locate_wire_component_before' event

* [develop]:+ Property sync overhaul in preparations for validation

* [develop]:+ Error response data only available when set

* [develop]:+ Nested property compatibility improvements

* [develop]:+ Acceptable Exception introduction

* [develop]:+ Form component introduction

* [develop]:+ Intersect plugin removal (its now in core AlpineJS)

* [develop]:+ Forms docs

* [develop]:+ Form message (i18n) translation feature (docs)

* [develop]:+ Form message displayment examples (docs)

* [develop]:+ 1.2.0 release preparations
* [develop]:+ Composer Rakit Validation require
* [improvement/property-binding]:+ WIP

* [improvement/property-binding]:+ Lifecycle upgrade to match Livewire

* [improvement/property-binding]:+ WIP

* [improvement/property-binding]:+ Array value change property binding

* [improvement/property-binding]:+ Code styling fix

* [improvement/property-binding]:+ Code styling fix

* [improvement/property-binding]:+ Code styling fix

* [improvement/property-binding]:+ Code styling fix

* [develop]:+ Constructor data also provided to the boot method

* [improvement/property-binding]:+ Binding Bugfix

* [improvement/property-binding]:+ Typo
* Automatically assign $magewire as template variable by @Vinai

Co-authored-by: Willem Poortman <mail@wpoortman.nl>
…agewirephp#26)

* [improvement/exception-handling]:+ Large exception handling overhaul

* [improvement/exception-handling]:+ Large exception handling overhaul (StyleCI fixes)

Co-authored-by: Willem Poortman <68-willempoortman@users.noreply.gitlab.hyva.io>
…n in v2) (magewirephp#27)

Co-authored-by: Willem Poortman <68-willempoortman@users.noreply.gitlab.hyva.io>
@wpoortman wpoortman changed the title Wire cache Draft: FPC support Apr 23, 2026
@wpoortman wpoortman added the V3 label Apr 23, 2026
@wpoortman

Copy link
Copy Markdown
Collaborator

Hey @toonvd,

I've started looking into this, and I came to the conclusion that I don't have enough knowledge of all the edge cases to be confident that I've tested this thoroughly.

With that in mind, I was thinking it might be a good idea to ship this as a separate module first, depending on Magewire, instead of merging it into the core right away. That would give it some time to mature and receive real-world feedback. Once we're both comfortable that it's stable and covers the necessary use cases, we could move it into the core and deprecate the standalone module.

Would that approach work for you? If so, would you prefer publishing it under the magewirephp namespace or your personal namespace?

Thanks!

@toonvd

toonvd commented Jul 26, 2026

Copy link
Copy Markdown
Author

Hi, let's do it under Magewire. Regarding behaviour above, I am planning to support both with a config change.

@wpoortman

Copy link
Copy Markdown
Collaborator

Awesome, let me make sure you'll get a repo to push to as soon as possible!

@wpoortman

Copy link
Copy Markdown
Collaborator

@toonvd

Please make a new PR on the magewire-fpc repository.

https://github.com/magewirephp/magewire-fpc

As soon as we can, we'll tag a first 3.0.0 release, maybe in beta... we'll see.

Thanks 🙏🏻

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.