ConversationContent type inconsistency

[victorchapado]

I found an inconsistency between the definition of the ConversationContent type definition and the component implementation. The definition declares the property as a React.Node but the implementation only accepts string:

source

{typeof lastSenderName === "string" && (
  <LastSenderName name={lastSenderName} />
)}{" "}

IMHO, I suggest continuing to accept a React node to be more flexible, something like this:

{typeof lastSenderName === "string" ? (
  <LastSenderName name={lastSenderName} />
) : lastSenderName}{" "}

Thanks!

[supersnager]

🎉 This issue has been resolved in version 1.9.8 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[supersnager]

@victorchapado thanks for your vigilance!