fix: rendering of ReactNode descriptions

[peetzweg]

Issue:

Closes #378

What has been done:

• description of ReactNode type wasn't rendered. It was treated as string.

Screenshots/Videos:

Before:

After:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sonner	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 27, 2024 4:33pm

[macalinao]

bump

[landg16]

@emilkowalski

[emilkowalski]

@landg16 Thanks for this!

[YashTotale]

When will this be released?

[zirlman]

@emilkowalski Can we expect this to be released soon?

[peetzweg]

@emilkowalski

[marcosfreitas]

I'm using the v1.5.0, and react 18, node 20.

@emilkowalski I saw that the contract was not updated, but based on the internal comparison you did, doesn´t this scenario pass?

I mean, my content is the same type that the description internally checks but in typescript, it does not work.

just checking, but I can workaround this with:

if (typeof content === 'object') {
  content = Object.values(content).join(' ');
}

toast.error('Could not save', { ...SonnerBottomRight, description: content, id: toastIDs.singleNotification })