Skip to content
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

Updated styles to resolve issue #15534, New severity not reflected in… #15908

Closed
wants to merge 1 commit into from

Conversation

chris-stillwell
Copy link
Contributor

… styles

Defect Fixes

This will resolve issue #15534 where the new danger severity does not have any style.

Copy link

vercel bot commented Jun 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
primeng ⬜️ Ignored (Inspect) Visit Preview Jun 25, 2024 7:01pm

@cetincakiroglu
Copy link
Contributor

Hi @chris-stillwell,

This issue is caused by a type mismatch in the message component. We've checked the styles in primeng-sass-theme repo where all component styles were generated and found that the styles are correct and classes should be -warn & -error. However, the message component should have 'warn' and 'error' severities instead of warning and danger as of 17.18.0 release. We've updated the type mismatch which will fix the issue in #15928

Thanks a lot for the effort and support you've put in with this PR, we appreciate it. However, since it isn't related to styles, I'm closing this PR. Don't hesitate to send PRs to make PrimeNG better!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Message: New severity not reflected in styles
3 participants