If you’re using Tailwind with React, what are your thoughts on @CSSHooks? Check it out first if you haven’t already. Would you switch? If not, why not?
@markdalgleish @CSSHooks The docs don't really do a good job at selling its usefulness. Hooks configuration is where you start to understand the value. Hover selector is not where it's at
@_jeroenpg @markdalgleish @CSSHooks I agree that `:hover` isn't that exciting by itself. For whatever reason, though, it's the main example people point to, historically: stackoverflow.com/questions/1316… What else should we highlight?
@agilecoder @markdalgleish @CSSHooks On the landing page you show a `dark` selector but it's unclear what it does. The examples on /configuration docs make it very clear to me how the library can help. Perhaps you can show the configuration part below, or have a basic + advanced example.
@_jeroenpg @markdalgleish @CSSHooks That's an excellent point. Maybe we could introduce tabs to toggle between usage and config? But, shorter term, what do you think about featuring @markdalgleish's idea of showing the actual media query?
@_jeroenpg @markdalgleish @CSSHooks That's an excellent point. Maybe we could introduce tabs to toggle between usage and config? But, shorter term, what do you think about featuring @markdalgleish's idea of showing the actual media query?
@agilecoder @markdalgleish @CSSHooks Introducing these tabs would tackle my concerns. Would that media query work without defining it as a hook? If it does then you could perhaps show it's equivalent to using `dark` in the previous example
@_jeroenpg @markdalgleish @CSSHooks Nope, you have to define it as a hook. But, you can eliminate any doubt about what a hook does by giving it the same name as its CSS representation. I was thinking a quick fix might be just to give all of the hook names on the homepage that same treatment...
@agilecoder @markdalgleish @CSSHooks I actually expected it would work automatically, if the key provided doesn't match any defined hooks. I don't think you should recommend developers to define the actual media query as hook. It's very error-prone e.g. missing a whitespace in `@Media (prefers-color-schema:dark)`
@jeroendotdot @markdalgleish @CSSHooks @Media That is a good point; but the hook name is type-checked, and I expect autocompletion would help people avoid the issue in the first place.
@agilecoder @markdalgleish @CSSHooks @Media Didn't really get the chance to say but props to you for creating the lib! It definitely peaked my interest!
@agilecoder @markdalgleish @CSSHooks @Media That does make it better, and you're right it probably will. What do you think about allowing raw css selector, without having to define the hook? If I only use a selector once, I don't want to define it globally. Is there a way to extend a HooksFn?