Chase Fleming

The component library I'm building is built on top of elem-go, with the overriding of styles and attributes available through the component props, but I guess I don't see a...

@bjartek, I'm intrigued by removing the `nil` concept for the `attrs` argument. One potential hiccup might be if someone places `attrs` in the middle of element children like: ```go content...

@whisk This is a great point to raise. I had actually already been thinking about multiple cases issue, but hadn't considered just the "if true do this, otherwise omit" case....

@gedw99 they are almost identical. The only difference is in the `Default` case. One being a function and the other following a similar syntax as the `Case`. And yeah fair,...

@whisk @gedw99 I just thought of one other non-breaking option: we could introduce a `None` function that you could use like so `elem.If(true, elem.Text("hi"), elem.None())` although you'd probably need to...

Sorry for the slow response. This issue required some thought. It's a tricky one. > So if you forget about "then" or "default" you wouldn't know about. > We can...

@nikpivkin The `Show` function in SolidJS did actually inspire what is now the `If` function in `elem-go`, and it was initially named `Show` as well. Re the package, looking at...

Good catch, yeah it looks like constants like `::before` and `::after` need to be added to [the constants list](https://github.com/chasefleming/elem-go/blob/main/styles/constants.go). If there are any issues with the double colon, it would...

So you're just appending the elements to the class? Yeah, I guess that would work. We could also do something like adding this to the `CompositeStyle`: ```go type CompositeStyle struct...

Awesome @whisk , thank you for taking this! Will check it out.