Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

💚 CLA has been signed

Welcome @victorst79!
Would you please sign the CLA linked below. Be sure to use the same email address linked to your Github account.
I'll get our CI (Jenkins, test this) started for you which will run our tests and get a preview built.

Can you also explain further the error you would receive?

Hi @cchaos !

The error occurs when in the Stat component in the description you add something other than plain text, for example I include my own component, doing this generates a <div> tag inside a <p>, for example:

<p><div></div></p>

This produces a problem with React validation, to be more exact it shows this warning in console:

Warning: validateDOMnesting (...): <div> cannot appear as a descendant of <p>.

Modifying the <p> tags by <span> fixes this error and so you can use custom components, even other Eui components within stats.

In reference to the CLA signature, I have signed it, I have downloaded the copy but it still marks the bot with a cross, is there any step that I have not done correctly?

Regards!

Sorry about the CLA comment, yes it is showing as complete. Github may not have refreshed. That's all good!

Regarding the error, I thought that might be the case. EuiStat is pretty prescriptive with the elements it renders because they're being wrapped in EuiTitle and EuiText components which should be some level of text element (heading, paragraph, etc).

EuiStat does accept children that aren't wrapped in any element. Would this suit your use-case?

If not, we will need to support some level of customizing these elements instead of just replacing the <p> tags with <span> tags. Is this something you'd like to take on, otherwise we can try to get someone to make these updates. It will require updating props, TS types, tests, and docs.

Hi @cchaos 👋

To put you in context, my problem is that within EuiStat I have a custom component that contains several text strings that allow me to filter directly with this information. It is a brief summary because it is a little complex to explain, my apologies.

In another order of things, I am not really good with unit tests, if you value my idea as positive and finally add it I would value it a lot.

Have a nice day!
Regards

We definitely value your idea @victorgs ! We'll just need to be sure we can be even more customizable with what element renders without possibly breaking any current implementations. What I'll do is create an issue for this, but close the current PR. Hopefully one of us or another community member can pick up the issue relatively soon for you.