- Issue created by @penyaskito
- Merge request !1083#3525608 Personalization Segment internal HTTP API integration → (Merged) created by penyaskito
- 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
I thought this was ready, but wait, we still need the auto-save integration.
Fixed issue summary. - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
wim leers → changed the visibility of the branch 3525601-personalization-segment-storage to hidden.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
wim leers → changed the visibility of the branch 3525601-personalization-segment-storage to hidden.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
🏓 Initial review — looking good! A few things can be simplified, and I spotted one bug AFAICT 😇
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Looking good! The key reasons for making :
- found a bug that would prevent the UI from working
- a lot of code duplication from XB's existing tests, let's share the non-trivial bits using base classes or traits
Looks like we'll land this later today! :D
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Looks like a solid step forward! 👍
IMHO the next most important thing on the Personalization front is the new
ComponentSourceplugin. 🤓🙏 -
wim leers →
committed de37bb4b on 0.x authored by
penyaskito →
Issue #3525608 by penyaskito, wim leers: Personalization Segment...
-
wim leers →
committed de37bb4b on 0.x authored by
penyaskito →
- 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
Yes! Moving to 📌 Personalization component source Active
📌 React UI for creating Personalization Segments Postponed and potentially most of 📌 React UI for editing segmentation rules in Personalization Segments Postponed are unblocked now!
Automatically closed - issue fixed for 2 weeks with no activity.
