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
When using the helpers provided by tailwindcss-primeui, the set prefix is not detected, so that all helper class variables are marked as '--p-something', which makes them undefined. Using the default prefix allows using the helpers, but will break every custom class created.
Furthermore, using the dark: class does not honor the darkModeSelector, instead it just does a media query (prefers-color-scheme: dark), resulting in patchy dark mode colors in a light mode theme.
Does anyone know if this is intended behaviour and why?
Could be that this is a me problem, but migration from v3 to v4 is anything but painless.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
PrimeVue v4 theming has options such as prefix, defaults to 'p', and darkModeSelector, which defaults to 'system'.
Here's my current options.
options: { prefix: '', darkModeSelector: '.app-dark', cssLayer: { name: 'primevue', order: 'tailwind-base, primevue, tailwind-utilities', }, },
When using the helpers provided by tailwindcss-primeui, the set prefix is not detected, so that all helper class variables are marked as '--p-something', which makes them undefined. Using the default prefix allows using the helpers, but will break every custom class created.
Furthermore, using the dark: class does not honor the darkModeSelector, instead it just does a media query (prefers-color-scheme: dark), resulting in patchy dark mode colors in a light mode theme.
Does anyone know if this is intended behaviour and why?
Could be that this is a me problem, but migration from v3 to v4 is anything but painless.
Beta Was this translation helpful? Give feedback.
All reactions