David Herman
David Herman
Currently, there really isn't any. The way I've been working on my Kobweb projects is with `println`s, because I could never figure out how to get breakpoints to work. And...
We should at least have a handful of relevant unit tests, if not an integration test or two, running on some sort of CI. Probably some sort of golden image...
Something like: ``` --- author: bitspittle --- This blog post was brought to you by {{ author }} ``` We'll need to think about this. This will really only work...
Right now, the Kobweb Application Plugin only runs on the current files of the current module. However, we want to ensure that users can refactor their code out to submodules...
Add a toggle switch widget (and maybe update the hello world site to use a switch instead of a button?)
Right now you can accidentally call it an extra time. Instead, the experience should be like: ``` $ kobweb run A server for this project is already running, which may...
See also: https://youtrack.jetbrains.com/issue/KT-10468 Right now, we have code like this: ``` ComponentStyle("...") { Breakpoint.MD { ... } } ``` and that should REALLY be implemented as an extension function with...
If a user creates a very very very large site, is there a way we can structure a project, maybe into multiple modules, to avoid having one gigantic js file?...
Right now we aren't too careful about people reading and writing to server/state.yaml and requests.yaml, but in the future we should do a better job protecting against multiple writes. We...