You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://forum.primefaces.org/viewforum.php?f=57
Codesandbox Case (Bug Reports)
Current behavior
The imperative Message API accepts custom markup for summary/detail, but if you use Message inline:
<Message severity="error" text="Field is required">
, then you only get the text property which is documented and typed as a string, not e.g. ReactNode (ts).
Message also doesn't render children.
In practice you can shove nodes into text:
Minimal reproduction of the problem with instructions
Please tell us about your environment:
React version:
PrimeReact version:
4.2.2
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
The text was updated successfully, but these errors were encountered:
mertsincan
changed the title
Message: accept node content for inline usage
Add content property to Message component
Aug 21, 2020
I'm submitting a ... (check one with "x")
Codesandbox Case (Bug Reports)
Current behavior
The imperative Message API accepts custom markup for summary/detail, but if you use Message inline:
, then you only get the
text
property which is documented and typed as a string, not e.g. ReactNode (ts).Message also doesn't render children.
In practice you can shove nodes into text:
, and it works, but it should be a documented feature.
Expected behavior
Message should accept custom node content in some way, e.g. as children:
Minimal reproduction of the problem with instructions
Please tell us about your environment:
PrimeReact version:
4.2.2
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
The text was updated successfully, but these errors were encountered: