Spent some of the weekend playing with an idea for a state management solution that takes advantage of all compose’s handy tricks. This was my first time playing with KSP and I didn’t bother trying to make it pretty, but I have a working demo enough to get a feel for it. I am pretty sure this violates some Compose best practices too 🙈
Anyway, maybe there’s some parts of this that could be salvaged for a real library.
https://twitter.com/zachklipp/status/1361472794312105987?s=21https://github.com/zach-klippenstein/compose-model
👍 4
👀 11
👌 2
t
Tash
02/17/2021, 3:30 AM
This is really cool @Zach Klippenstein (he/him) [MOD]!! Been meaning to play around with KSP; curious, what was your experience like with the KSP API?
z
Zach Klippenstein (he/him) [MOD]
02/17/2021, 4:18 PM
It’s pretty great. Kdoc on most things, and supplemented with the docs on GitHub it was really easy to figure out.
🙌🏼 1
Compared to the psi and Android lint apis, everything more or less did what I expected and so it felt a lot more productive.
🙌🏼 1
c
Colton Idle
02/18/2021, 3:45 AM
@Zach Klippenstein (he/him) [MOD] This is awesome. Good work!
z
Zach Klippenstein (he/him) [MOD]
02/18/2021, 3:52 AM
I think the ergonomics are promising. I’m really not thrilled about the complete lack of compile time safety around heterogenous Applier types, and it sounds like beta has been cut so I don’t think there’s gonna be any fix for it. Really too bad, it limits the number of different practical uses for compose in a single codebase.