Send page data to Drupal for storage in auto-save store

This looks good but when I try to manually test it I get errors. Investigating

Created related #3498219: Missing E2E test for Publish button hides bugs

working this

I have fixed the bugs I found in manual tests. Now in manual testing change update the page data fields(at least have tried title and body) the "Publish" button works, and when I view the node outside of experience builder I see both the XB and other field changes.🎉

Assigning back to @wim leers since @larowlan assigned to him but I will continue to review.

I have idea why the test is failing. Will work on it

PHPUnit tests are passing now, the e2e contextual-panel.cy.js test failed, Hoping was just a fluke so retesting

UPDATE: yep green now

I think this is good now, I started this and @larowlan did a lot of the work too, so I can't approve

I didn't get to this today, between tying up the many loose ends that #3486203: Integrate saving sections with the backend: (de)normalize Pattern config entities using the client-side data model revealed, which I finished up just now in #3484678: Simplify ComponentSourceInterface::getClientSideInfo(), introduce ClientSideRepresentation value object, and leverage it (thanks, @longwave!).

I had deprioritized reviewing this issue in favor of other issues: because I need to see the big picture to be able to properly review this, and pretty much all of this infrastructure landed while I was on paternity leave with no involvement from me. That's why I've been asking @tedbow to update https://www.drupal.org/project/experience_builder/issues/3455753#save-dr..., which he has been doing! 👏

I promise a thorough review tomorrow.

Meanwhile, this seems to have conflicted with #3499774: Cannot save Page in XB when content_moderation is installed, so a rebase would be appreciated 🙏😊

Thanks!

(Also thanks to @tedbow for getting https://www.drupal.org/project/experience_builder/issues/3455753#save-dr... in good shape!)

Posthumously reviewed the predecessor

Reviewed the #3487484: Save page data form values in application state with support for undo/redo MR to be able to review this one. High-level observations from there:

• \Drupal\experience_builder\Controller\ApiLayoutController::getEntityData blew my mind.
• Editing the node title in the Page data tab does not result in the auto-saved entity getting its label updated (nor does it result in an updated preview, but that'd be the page title block needing to get updated — for that we have #3491701: [later phase] ApiLayoutController must use the previewed route's controller, and override canonical content entity routes' received entity object 👍
• I would've liked #3497669: Extend test coverage for checkboxes + radios to be a blocking issue, because A) adding those was out of scope and caused confusion on the issue, B) now we risk never getting to those. Which increases technical debt/risk. That's something we need to get better at everywhere though, but in an MR as complex as this one, I think we as a team need to become more disciplined at that.
• In other cases, the temporary work-arounds in the code do not point to the fixing issue, example: #3487484: Save page data form values in application state with support for undo/redo.
• Updates/additions to docs/ would've been nice 😇🙏 A lot of the React code is beyond me, especially because comments are sparse.
• 🤩 Impressive work on undo-redo-timeline.cy.js and all the things it proves! Undoing across both the edited content entity object's fields and the XB component tree ("layout+model") is crucial, and it now works!

Review

1. Some really impressive work here, @larowlan and @tedbow! 😄👏 It looks pretty hacky at this point, but that's because we're bootstrapping all this. I'm confident it'll get better over time. 👍
2. Bug #1: When the server responds with validation errors, those are not displayed anywhere: not in the Publish button (that's in scope for #3497530: Implement the "Publish All" button, and not in the form. I cannot find an issue for that.
3. Bug #2: Buggy behavior for boolean fields, as described in detail at https://git.drupalcode.org/project/experience_builder/-/merge_requests/5....

Can you please create a follow-up issue for those 2? 🙏

Given how important this is for https://www.drupal.org/project/experience_builder/issues/3455753#save-dr..., and that this definitely gets us to a better place than HEAD: merging :)

Thanks for those! 🙏

I quite liked/was impressed with that "hacky dance" 😅🙈 IDK what that says about me 🤣