-
Notifications
You must be signed in to change notification settings - Fork 85
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
Message -> from version 17.16 no more "error" but "danger" #134
Comments
@cetincakiroglu If necessary I could make a PR easily....tell me. |
Still relevant in version 17.18.0 |
Hi, Thanks for reporting the issue. Correct severity options for the message and toast components should be as follows:
Possibly, this issue stems from a problem occurring when merging branches in PrimeNG repo. Styles are correct, classes should be -error & -warn. This issue will be fixed in PrimeNG 17.18.3 release this week. |
@cetincakiroglu Still relevant in version 17.18.4 |
The latest version of Primeng just replace "error" message type with "danger" one:
https://github.com/primefaces/primeng/blob/master/src/app/components/message/message.ts#L39
So basically sass doesn't work anymore:
primeng-sass-theme/theme-base/components/messages/_inlinemessage.scss
Line 39 in b47e885
I still don't catch why primeng demo site doesn't use this package!
The text was updated successfully, but these errors were encountered: