Allow components to use textarea in favor of input

How about

diff --git a/tests/modules/sdc_test_all_props/components/all-props/all-props.component.yml b/tests/modules/sdc_test_all_props/components/all-props/all-props.component.yml
index 1544192f..6e6e1643 100644
--- a/tests/modules/sdc_test_all_props/components/all-props/all-props.component.yml
+++ b/tests/modules/sdc_test_all_props/components/all-props/all-props.component.yml
@@ -11,10 +11,19 @@ props:
       examples:
         - true
     test_string:
-      title: 'String'
+      title: 'String — single line'
       type: string
+      # Implied pattern:
+      #pattern: '.''
       examples:
         - Hello, world!
+    test_string_multiline:
+      title: 'String — multi-line'
+      type: string
+      # @see https://json-schema.org/understanding-json-schema/reference/regular_expressions
+      pattern: '(.|\r?\n)*'
+      examples:
+        - "Hello,\nworld!"
     test_REQUIRED_string:
       title: 'String'
       type: string

And we can make that simpler of course, for those who prefer that:

    test_string_multiline_ref:
      title: 'String — multi-line ($ref)'
      type: string
      $ref: json-schema-definitions://experience_builder.module/multi-line-string
      examples:
        - "Hello,\nworld!"

or perhaps even multiple aliases, for example:

    test_string_multiline_ref:
      title: 'String — multi-line ($ref, alias)'
      type: string
      $ref: json-schema-definitions://experience_builder.module/textarea
      examples:
        - "Hello,\nworld!"

Something like $ref: json-schema-definitions://experience_builder.module/textarea would probably make sense 👍

1. I added the new JSON schema definition: https://git.drupalcode.org/project/experience_builder/-/merge_requests/2...
2. I updated the all-props test SDC: https://git.drupalcode.org/project/experience_builder/-/merge_requests/2...
3. I updated \Drupal\experience_builder\SdcPropJsonSchemaType::computeStorablePropShape(): https://git.drupalcode.org/project/experience_builder/-/merge_requests/2...
4. It shows up:

Less than 10 minutes 👍

Next step: updating \Drupal\Tests\experience_builder\Kernel\SdcPropToFieldTypePropTest to expect more results.

@lauriii, is that sample in all-props.component.yml to your liking? 😊

… and now I've actually finished implementing this completely, because:

1. Update StringLongItemOverride to specify an additional validation constraint that conveys newlines are actually allowed, allowing it to match against json-schema-definitions://experience_builder.module/textarea … is enough to make it all work 😊

Ready for final review now 😄 @tedbow is the only other person who's been delving into this area, so assigning to him.

Looks good. 1 suggestion to make how this works clearer

Add my small suggestion

Really nice to see we were able to land this issue this quickly! 🚀 Great team work @Wim Leers and @tedbow! 💯 👏

Note: the front-end does not yet allow typing in the <textarea>. Root cause TBD.

We have 🌱 [META] Redux sync on ALL prop types, not just ones with a single [value] property Active for that, unless @lauriii decides to increase the scope of 📌 Component props form: map textarea, bool, and select elements to React components Fixed .

Should there be a follow-up issue to add textarea schema refs to any of the existing XB components so there is an example?