Disallow empty string example values in Code Component metadata files
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3587397. -->
Reported by: [balintbrews](https://www.drupal.org/user/613760)
Related to !1001
>>>
<h3>Overview</h3>
<p>The ESLint and CLI validation doesn't cover string prop example values in <code>component.yml</code> files, where adding an empty string causes issues. The backend schema validation shouldn't let that happen, and the CLI push command should fail, but it currently doesn't: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3587211" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3587211</a></span>.</p>
<p>Even with that backend issue fixed, it's a much faster feedback if validate with ESLint.</p>
<h3>Proposed resolution</h3>
<p>Extend <code>@drupal-canvas/eslint-config</code> in the <code>required</code> config with a new rule that reports empty string example values for <code>string</code> props and arrays of strings.</p>
<p>Also rename the existing image example URL rule from <code>component-image-example-urls</code> to <code>component-prop-example-value-image-url</code>.</p>
<h3>User interface changes</h3>
<p>n/a</p>
> Related issue: [Issue #3587211](https://www.drupal.org/node/3587211)
issue