Simplify ApiAutoSaveController::post for page regions

Glad I didn't add elseif in the suggestion, nice branch name 🤣

Makes sense, better to be safe than sorry - thanks

There's a bit I don't understand yet 🙈

I don't feel that strongly, though, but a) there's no UI for creating regions; b) those are created when they are enabled for the theme in its settings, so feels safer to ensure they can't be created.

It's not that I feel strongly, it's that I don't understand why PageRegion is special-cased compared to all others. Because … all auto-saves are for updates to content & config entities only? IOW: it's impossible to create.

Looks like the enforceIsNew(FALSE) was introduced in 📌 Implement auto-save of the page template config entity Active . Will figure out which commit and why.

P.S.: only now see the branch name 🤣🤣🤣🤣🤣🤣🤣👏

Commit found: by @larowlan: https://git.drupalcode.org/project/experience_builder/-/merge_requests/4...

Tried to generalize: https://git.drupalcode.org/project/experience_builder/-/merge_requests/1...

That worked :)

@penyaskito: Do you agree with the tweak I made? If so: go ahead and merge! If not: what am I missing? 😄

Ship it!

I can't merge 😉

@penyaskito and I paired to debug why he can't merge. Even after granting him all the d.o permissions and loosening GitLab settings, he still can't merge, whereas he really should be able to. Either GitLab is broken or d.o's integration with it 😬

Merged for him! 🚀

Automatically closed - issue fixed for 2 weeks with no activity.