I'm hoping this library is not too much of an abstraction, more of a typed 1:1 mapping. With a layer like this established, it would be easier to build a library on top.
That said, I'm not opposed to adding convenient helper functions where needed. On Apr 18, 2017 1:02 PM, "'Rupert Smith' via Elm Discuss" < [email protected]> wrote: > On Tuesday, April 18, 2017 at 2:20:20 PM UTC+1, Jakub Hampl wrote: >> >> RE: strokeWidth - that's a bug, the attribute is actually called >> stroke-width >> <https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-width> >> . >> > > Yes, thought that might be it. I'll create github issues for bugs that I > spot from now on. > > Which way is preferable for styling SVG? CSS or attributes? Is it > desirable for the API to abstract this away and just present one way of > doing it, or best to expose the guts of it and let the user choose? > > -- > 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. > -- 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.
