#ajax config not reliably implemented for consecutively added components

Is this not at the Semi-coupled theme engine level? 🤔

The problem is due to Redux createAPI() caching requests to xb/api/form/component-instance -
Any component form visited the first time will work.
If the component form is revisited in the same page visit, it will return the cached version which does not have the same selectors as those in drupalSettings.ajax and the ajaxification of elements such as "Add media" does

This is e2e testable but might be worth considering holding off on that since we might be switching testing libraries in the near future, and this is only a few lines in one file that can be manually tested pretty easily.

Did not mean to switch the priority

Left a question on the MR, feel free to mark as fixed if that's not a valid question or alternatively we could explore that approach in a follow up if it is a reasonable idea

The problem is due to Redux createAPI() caching requests

🤯

I agree with @larowlan's remark on the issue and added a bit more info to it.

See MR comments, tl;dr @bnjmnm is correct we don't have the form build ID at that point

FYI: this issue caused a (perceived?) performance regression: 🐛 Regression: loading state when navigating between components Active .