I built a small app using elm-css to spin the wheels. One of the things I'm looking for is a "compiler's got my back" kind of experience with CSS; however, I found a couple of oversights. I'm curious if there are some best practices that might have given me a better experience:
1. I accidentally used an `id` where a type was meant to be a `class`. When defining types to be used in elm-css, it's a simple type enumeration. Then you define whether it's a CSS id (#) or CSS class (.) I would have expected (somewhat magical thinking, perhaps) that I would not be allowed to put a CSS id in a `class [ myCssId ]`, or a CSS class in a `id myCssClass` context. 2. It appears there is no way to be certain at compile time if the `*.css` file is up to date. I'm using the `elm-live` local development server, and I see no way to guarantee that I'm working with the latest CSS definitions. In other words, my Elm files may be typed and correct, with the compiler reporting no errors, but the browser can show incorrect styles if the css file(s) are not up to date. Are there any best practices around these issues? Thanks, Duane -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
