@kakatohesss https://t.co/W2b4vRP2ay - building Vizguard: visual regression testing without Playwright. Record the flow in the browser, replay after every deploy, see exactly what broke.
@csaba_kissi https://t.co/KmjwYu1ExA - building Vizguard: visual regression testing without Playwright. Record the flow in the browser, replay after every deploy, see exactly what broke.
While I could create a `.primary` class and reuse it on every button, I am attempting to achieve the desired effect where the `variant=“primary”` attribute applies all necessary styling, resulting in a clean HTML structure.
During the development utilizing Flux UI, I encountered some confusion regarding the optimal styling practices for button variants with a value of “primary.”
Is this approach effective or if there are alternative methods to achieve the desired styling. @calebporzio
Publishing a component may be an option, it appears to be an excessive approach for a simple styling requirement. Alternatively, I could incorporate all Tailwind classes for the button, but this would necessitate repeating a significant portion of the code.
I got the Flux UI kit through the BF deal, and wow, I wish I’d jumped on this sooner! The UI kit is fantastic. The file upload and text editor features are so much faster—no more wrestling with npm packages and other headaches. It’s a truly great product!
@calebporzio