#Starshot

Great job. Merged!
Thanks again!

We also need to deal with recipe translation. We should see if there is an issue and if not open one. It's going to be complex.

I discussed this with @alexpott in Zoom today.

Long story short: this issue can proceed as it currently exists, but there needs to be a longer-term plan to unify the messy solar system that consists of Typed Data, config schema, the form system, and CLI input. Drupal doesn't have a single generalized "data input, validation, and translation system" that we could leverage, really. The recipe system leverages Typed Data in a reasonably pure way, but as the current patch demonstrates, that necessitates encoding form API elements into recipes if we want them to be presented in a particular way in a particular context. It would be so much better if I could just say "this input is a string with these validation constraints", and trust that Drupal would be able to present that input appropriately in the CLI, in a form, etc.

But we're a long way off from that.

So we decided to be pragmatic as ever, and implement the proposed approach. Hopefully we can deprecate it as core's ability to handle input in a unified way becomes more robust. But for now, this is the clearest way for us to deliver this essential feature.

I think this is all the test coverage we need. Looks good to me.

Hello,
I am not able to reproduce the issue getting error while applying patch.
Please see the attachment.

Hi,
I am not able to reproduce the issue before applying patch.
Please see the attachment.
NotReproduceable.png

Fixed patch for 1.35

Updated patch for 1.35 to use in Drupal CMS search track recipe

Not postponed, both are related to the Drupal CMS Dashboard track.

Merged in. Thanks for everyone's help on this issue.

Updating this to target the 4.2.x branch.