Enhancement/2122 add description to array renderer

[SaSteffen]

As discussed in #2122: This is a minimal change that renders a description for primitive and object array renderers in React MUI.

The Primitive example looks like this:

The other one looks like this:

As discussed, I just used a FormHelperText. We could achieve similar results using custom typography elements probably.

[CLAassistant]

All committers have signed the CLA.

[netlify]

✅ Deploy Preview for jsonforms-examples ready!

Name	Link
🔨 Latest commit	9c0780d
🔍 Latest deploy log	https://app.netlify.com/sites/jsonforms-examples/deploys/659d76102882e00008ef3159
😎 Deploy Preview	https://deploy-preview-2227--jsonforms-examples.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sdirix]

Hi @SaSteffen, thanks for the contribution ❤️ We will take a look very soon

[coveralls]

coverage: 84.798% (+0.003%) from 84.795%
when pulling 9c0780d on SaSteffen:enhancement/2122_add_description_to_array_renderer
into c8d3ecf on eclipsesource:master.

[sdirix]

Thanks for the contribution! The PR looks good overall.

I have two change requests:

• Make sure to not render the FormHelperText at all if there is no description
• Add a test case for the existence of the description when given

[SaSteffen]

@sdirix Sure. Added the conditional rendering and the two tests.

[sdirix]

We need to use && instead of ?? as ?? short circuits and will use the description as is and not with the FormHelperText.

Is it possible to search for the FormHelperText element in the tests too?

[SaSteffen]

We need to use && instead of ?? as ?? short circuits and will use the description as is and not with the FormHelperText.

Sorry, of course.

Is it possible to search for the FormHelperText element in the tests too?

I checked the DOM and it does not generate any element around it, even if the FormHelperText has an id attribute. If you prefer, I can put it in a div and use that one in the tests.

[sdirix]

I checked the DOM and it does not generate any element around it, even if the FormHelperText has an id attribute. If you prefer, I can put it in a div and use that one in the tests.

I used nested selectors to check for the respective elements. I also added tests checking for the non-existence of them in case there is no description.

[SaSteffen]

I checked the DOM and it does not generate any element around it, even if the FormHelperText has an id attribute. If you prefer, I can put it in a div and use that one in the tests.

I used nested selectors to check for the respective elements. I also added tests checking for the non-existence of them in case there is no description.

That leaves nothing else to be done, right? Thank you for the support.

[sdirix]

Thanks for the contribution ❤️