Paul Smith
Paul Smith
https://github.com/mvdan/gofumpt
This doesn't need to implement all the Language Server Protocol capabilities to be useful. I think just having code completion and syntax highlighting would be 95% of what we would...
Currently if Pushup encounters any error, including a normal parse error while a developer is typing and saving, that causes the program to exit, this also causes the developer live...
Pushup pages don't depend on each other and so are a good candidate for compilation in parallel in separate threads.
Pushup should model good ops behavior, so should have healthchecks out of the box. These can be both internal Go code implementations of a healthcheck interface and a registered HTTP...
Pushup currently responds with short plain text status message when handling a 404 or 500. It should detect whether the project has page(s) to respond with. These should be in...
Pushup compiles down to Go code in its own package that should be easy to import in other Go projects that would like to get the features Pushup provides. Right...
Add cross-site request forgery protection. I like the way [Django](https://docs.djangoproject.com/en/4.1/ref/csrf/) does it. Since we compile the template the form is in, we could provide automatic rewriting of the HTML to...
This currently doesn't work as you might expect, and is ill-defined. The codegen generates one partial type implementing Responder, but its output is wrapped in the `for`. It's not really...
#30 brought up how handling a trailing slash should work. Should it be the default to have a trailing slash in URL paths, and redirect if a request would have...