@ddunderfelt@adamwathan Mmm i haven't had that experience at all because you can have classes defined by yourself, so it wouldn't be too smart for the LLM to just guess they don't exist; but i rarely just let the LLM take the wheel, i usually go step by step with it
@ddunderfelt@adamwathan There's barely any breaking change in that regard, no? Outside of tw's setup, just some utilities like `rounded-sm` and other very specific things. So you'll be able to just continue using any LLM pretty much like always.
https://t.co/uhCb2Mhy8Z
@justalexoki@jxnlco Damn i've been getting the opposite: inline many times tries to create a few-lines solution which is shite and doesn't make sense in context.
@mhdcode Huh, interesting approach. Definitely makes sense, though it's a tad bit less explicit maybe? (I have to make sure the elements match up between the layout and the logic, instead of this being a given. It's closer to how you'd do it in classic JS / JQuery i guess.) Thanks!
@cramforce I was just thinking of the inlined CSS thing the other day and i wondered if i could do that in Next.js, given that i always use Tailwind so it feels obvious. Given this experience, has there been talk to giving some easy config to achieve something like that in Next.js? Thanks!
@vvoyer Of course! I was talking about _my_ users, and how i decided i chose to remove this complexity from my code base. If i ever want it back i'll surely look at how you did it, thank you for sharing.