195 karma · joined October 9, 2025
Also, yes I agree, RequestContext makes more sense!
Thank you, I'll will implement that :)
Yes it's on the backlog and will be fun to implement :)
I did intend to implement parallelization as a later feature so it's good to bring it up.
I will add it to the backlog of things to do :)
There are some more examples in doc/
Appreciate you saying that!
I'd love to hear about your project when you get round to it.
The 'appRoute' is a macro that expands to a function signature.
The macro is: '#define appRoute(name) HttpResponse name(AppContext ctx)' and the parameter I passed as 'home' is expanded into the function name. The reason is because all controller function signatures are the same, so just writing 'appRoute' allows the developer to save time writing endpoints!
It is a tradeoff between readability and development speed. And one of the ideas behind the framework is succint and minimal code.