Will passing the model props for a component via GET parameters hit limitations due to URL length

Had a shot at using PATCH for this, but not sure what impact it will have on subsequent AJAX requests.

Yep, doesn't work with AJAX forms because the form needs to be rebuilt and that requires the params - and they are no longer in the body of the request because now we're POSTing the Drupal form

That was far too easy

Ok, added a hidden field with those values to ensure it works with AJAX.

Yes these can be tampered, but so could the URL so 🤷

Maybe we need an anti-tamper hash?

Is this for URLs where we're saving the submission to autosave storage? If so, GET is incorrect HTTP semantics, not only length constrained.

This is for when we fetch the component inputs form

wim leers → made their first commit to this issue’s fork.

LGTM, just a minor remark about the changes in inputBehaviors.tsx (https://git.drupalcode.org/project/experience_builder/-/merge_requests/6...) being AFAICT avoidable and in a way that makes XB slightly more robust.

I self-addressed that with a trivial commit, resulting in a tighter scope that make me comfortable merging this: https://git.drupalcode.org/project/experience_builder/-/merge_requests/6....

I was also concerned about this a while back but this is a neat solution and much simpler than I expected it to be! Two minor points, one that can wait until later, the other is just a naming issue, otherwise this looks great to me so leaving at RTBC.

Merged per https://git.drupalcode.org/project/experience_builder/-/merge_requests/6...

@longwave's concerns about special casing the form_-prefixed key-value pairs are accurate, but it's pre-existing. This doesn't make that future problem harder, but keeps it identical.

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