ServerClientConversionTrait

@tedbow added ClientServerConversionTrait in ✨ AutoSave Entity Revision POC Active .

I know that @larowlan has a clear idea in his head for how we should approach this. (In another issue I commented in the past hour he was talking about a PHP value object to contain the client-side data model — but I can't find it now 😭)

Alternatively, I could imagine ::toClientSideRepresentation(): ClientSide and ::fromClientSideRepresentation(ClientSide $representation) being added to:

• ComponentTreeItem
• PageTemplate
• Pattern
• …

… and for them to share common logic using a trait.

I'm curious what @larowlan thinks 😊

@larowlan: perhaps you think we should close this in favor of 📌 Add a param converter and DTO for XB data model Active ? :)

While working on 📌 Improve or remove ComponentSourceInterface::getClientSideInfo() Active , it became clear that a related challenge appeared there, which relates closely to what I wrote in #2. See https://git.drupalcode.org/issue/experience_builder-3484678/-/tree/34846..., described in #3484678-20: Improve or remove ComponentSourceInterface::getClientSideInfo() → , @larowlan 🤓

ClientSideRepresentation landed in 📌 Improve or remove ComponentSourceInterface::getClientSideInfo() Active , but it's kinda like JSON:API's CacheableNormalization.

It's not doing the much more advanced transformation that this issue is suggesting/implying. But … I'd definitely be interested in seeing it evolve towards that.

Curious to read @larowlan's thoughts!

Looking good Wim, great stuff