UNSAFE classname test

[pavelklibani]

Description

• Our Spirit components still require UNSAFE_className, UNSAFE_style
• Third party components required their own props - className, style, etc.

Warning

Some components are still broken and will need to be fixed in upcoming changes.
The problem is that some components spread their props, while others combine classes inline.

Additional context

Note

Testing demo available at Next.js app router: http://localhost:3000/test1

Issue reference

(UNSAFE_)className v elementType komponentach

[netlify]

✅ Deploy Preview for spirit-design-system ready!

Name	Link
🔨 Latest commit	ca89643
🔍 Latest deploy log	https://app.netlify.com/sites/spirit-design-system/deploys/6762e1682b87830009e119ba
😎 Deploy Preview	https://deploy-preview-1826--spirit-design-system.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 (🔴 down 1 from production) Accessibility: 91 (no change from production) Best Practices: 100 (no change from production) SEO: 91 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for spirit-design-system-storybook canceled.

Name	Link
🔨 Latest commit	ca89643
🔍 Latest deploy log	https://app.netlify.com/sites/spirit-design-system-storybook/deploys/6762e1683725fc000858795e