Message: New severity not reflected in styles about primeng HOT 6 CLOSED

This is really annoying and concerns every component with a severity input. This is a really annoying breaking change in a minor release :(

from primeng.

Temporary solution for typescript that corrects the style, but displays an exclamation icon instead of times icon.

[severity]="$any('error')"

from primeng.

Related to primefaces/primeng-sass-theme#134

from primeng.

Hi all,

As of 17.18.0, correct severity options for the message and toast components should be as follows:

severity: 'success' | 'info' | 'warn' | 'error' | 'secondary' | 'contrast' | undefined;

Possibly, this issue stems from a problem occurring when merging branches. We'll address the issue in 17.18.3 this week.

from primeng.

After updating primeNg to the new version, we have the same problem. I can see that for message severity error is no longer supported and instead takes danger, however the component displays badly because the theme css message still uses error and not danger.

from primeng.

With typescript it leads to an compile error:

error TS2322: Type '"error"' is not assignable to type '"success" | "info" | "warning" | "danger" | "help" | "primary" | "secondary" | "contrast" | null | undefined'.
<p-message severity="error"

from primeng.