David Herman

Looks like this may have broken with Compose 1.2.1

So I *finally* got a chance to look into this, nearly one year later :) With the way Kobweb has evolved, it's possible that KSP may not be the approach...

I'm going to close this for now. I think having the Gradle plugin continue to do the parsing is the easiest path forward. Otherwise, I'd need to ask users to...

One thing that might make this worth revisiting is KSP probably has better support for resolving values? Like, if I have ``` val SomeVariant = SomeStyle.addVariant("...") ``` and I want...

Note that Kobweb is now updated so latest (0.10.0+) targets later versions of Kotlin and Compose. I'm going to mark this as closed, because it should have been fixed long...

This bug was originally about `spacedBy` but I'd like to support all of: * SpaceAround * SpaceEvenly * SpaceBetween * spacedBy(...) The first three should hopefully not be too bad,...

* ~~SpaceAround~~ * ~~SpaceEvenly~~ * ~~SpaceBetween~~ * spacedBy(...) Supporting the three crossed off arrangement values was easy. There already was a direct CSS support for them. `spacedBy` will require another...

We're no longer using jgit but instead are delegating to git on the user's system. Seems to be working for a while now!

Has there been any discussion of simply disallowing unnamed context parameters? Unless I'm mistaken, this would eliminate... 1. The awkward `summon` function 2. The need for a new empty `context`...

Having processed my thoughts a bit more, and talking with some friends, I can see the value in an unnamed context parameter, so I partially retract my previous comment. (For...