Allow react components as message without react prop types error

[james-cordeiro]

You'll notice that the message param of enqueueSnackber allows react components such as <span>I am <strong>STRONG!</strong></span> to be passed in rather than just a string. It works perfectly fine too but a React prop invalidation error is thrown. This change stops that from happening.

[iamhosseindhv]

Thanks for the contribution @james-cordeiro 👍🏼

[slavikdenis]

@iamhosseindhv could you fix ts types please to allow this? :) thank you

[iamhosseindhv]

this has been merged into master all be published in the next version release @slavikdenis

[slavikdenis]

Great, thanks :)

[iamhosseindhv]

Actually this has already been published. @slavikdenis

[slavikdenis]

Currently I am using "notistack": "^0.4.1" and the problem in index.d.ts is this
export interface InjectedNotistackProps { onPresentSnackbar: (variant: VariantType, message: string) => void; enqueueSnackbar: (message: string, options?: OptionsObject) => void; }

[slavikdenis]

Where it should be enqueueSnackbar: (message: React.ReactNode, options?: OptionsObject) => void;

[iamhosseindhv]

You're right @slavikdenis . This has been fixed in PR #40 and will be released in the next version.

[slavikdenis]

Oh I see! Great :)