feat: Allow ReactNode as children/content of the Toast - closes #6038

[Rados51]

Closes #6038

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

yarn jest

[snowystinger]

Thanks for the PR!

Question to the team. Do we actually want to allow ReactNode? or should we only allow strings and then parse the strings for b/i/etc and render that ourselves?
Previous concerns were that we didn't want to allow other interactive elements inside a toast. Nor things like images/spinners/etc.

[Rados51]

@snowystinger

If the team decides for text parse, is it okay to use additional property in options (like allowHtmlParse) to skip unnecessary RegEx checks for better perf?

[snowystinger]

I was thinking very simple. IE, only allow bold.
I'm not too worried about perf, it's a short string for an element that doesn't appear frequently and shouldn't rerender much.

[Rados51]

I guess that would be good to include also a span tag for the possibility of adding class to specific parts of the text. Might not be up to Adobe internal guidelines, but useful for third-party.

[snowystinger]

We should be talking about this later this week.

However, you brought up an important point. Which is that this is useful for non-spectrum users. We intend to make a RAC toast implementation which should alleviate this particular use case.