Over at 🐛 Page status changes from "Published" to "Changed" even when no actual changes are made Active , I did some tightening of the "collapse/uncollapse" logic. In doing so, I (unintentionally):
However, the tests that 📌 Code Components should render with their auto-saved state(if any) when rendered in the XB UI Active introduced are failing now, with the following exception:
OutOfRangeException: 'voice' is not a prop on the component 'Code component: Hey there'.
… because those tests intentionally were populating a voice prop that
JavaScriptComponentHowever, this never really made sense, but especially no longer since we introduced component versions. It never made sense though, because no entry would exist in prop_field_definitions for the code component's Component config entity, meaning no widget would ever have appeared in its component instance form!
So while in a way HEAD's behavior was good for robustness and #3529622 "almost broke that", it's actually only allowing incorrect values AFAICT.
\Drupal\experience_builder\Plugin\ExperienceBuilder\ComponentSource\GeneratedFieldExplicitInputUxComponentSourceBase::collapse() like so:None.
Active
0.0
Component sources
, not , because by just using the UI, it is not possible to trigger this scenario. Only manually crafted requests could hit this.
the issue summary says 'change like so:' but is missing the changes