- Issue created by @penyaskito
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Let's rebase to exclude all the things that have been merged in the meantime 😊🙏
- 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
TBH was a full PoC. Just the last developments of the new ComponentSource ideas broke other things ^_^ and didn't update yet.
I plan to update this tomorrow morning and maybe spend some time here. - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
I see — that's the bit I wasn't sure of :)
Even then, it would be great to rebase this, even if it's only to A) remove the parts that are already merged, B) then narrow the focus to just the
ComponentSource
! 🙏 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
This has served its purpose! Many parts landed. The concrete implementation successor of this is 📌 Personalization component source Active .
- Assigned to penyaskito
- Status changed to Closed: outdated
16 days ago 2:39pm 1 August 2025 - First commit to issue fork.
- 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
MR !1404 is up-to-date as of today and works, which can help as a reference for the different implementation tickets.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Note: this PoC is a continuation from before #3525746-6: Update the React client preview view → was the agreed upon consensus for how to build this — consensus between @effulgentsia, @penyaskito and @jessebaker.
(Linking to improve discoverability even though this is closed, because @jessebaker and @penyaskito are using this closed issue/MR to get this functionality going again.)
- First commit to issue fork.
- Merge request !1Draft: [DO NOT MERGE] FE Personalization PoC #3525565 → (Open) created by penyaskito