-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MultiSelect emptyMessage prop results in error #5340
Comments
Its working for me? https://stackblitz.com/edit/react-9h4sys?file=src%2FApp.js I don't see any errors in the log? |
Please fork the CodeSandbox project or Stackblitz project and create a case demonstrating your bug report. This issue will be closed if no activities in 20 days. |
oh, i see this error in your demo and i have a same issue with him, i'm using nextjs 14.0.3, primereact 10.1.1 |
@Chuazz that helps! Found and fixed for next version. |
niceeeee |
* Fix #5384: TreeTable support hidden columns * fix:#5553:TreeTable: need to be converted to data- lookups instead of className lookups * TreeTable * Fix #5597: TreeTable body align * Fix #5393: Tree propagate icons to leaf nodes * Fix #5233: Cell editor ColumnEditorOptions param fix * Fix #5398: Slider with min value rendered incorrectly * Fix #5340: MutliSelect emptyMessage don't add to DOM * Fix #4190: Chip aria fixes * Fix #5414: p-disabled for svg icons * Fix #5424: CascadeSelect use data instead of CSS selector * Fix #5425: CascadeSelect fix for StrictMode * Fix #5440: InputText only print className once
Describe the bug
It seems like the emptyMessage prop hinted by the documentation does not work.
React does not recognize the 'emptyMessage' prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase 'emptymessage' instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Reproducer
No response
PrimeReact version
10.0.9
React version
18.x
Language
TypeScript
Build / Runtime
Create React App (CRA)
Browser(s)
Chrome
Steps to reproduce the behavior
Expected behavior
No response
The text was updated successfully, but these errors were encountered: