David
Thanks for your feeddback @jbuhacoff, how do you feel about ```kotlin fun main() { val javalin = Javalin.create { app -> app.router.get("/hello") { ctx -> ctx.result("Hello, World!") } } }...
> but it's still an entry point for app config. I agree, it's "app config", which is why I called it `app`. This is similar to ``` config.staticFiles.add(staticFiles -> {...
> Yes it does, because for all of these options you wouldn't hold a reference with the same name, as you would do for your app config, which effectively also...
The old `app` instance will basically not have any methods anymore, just `.start()`. I think `app` reads a lot more natural than `config` here: val javalin = Javalin.create { app...
@p4paul this should be easy enough to add as a feature, would you like to add it?
# (≖_≖ )
Previously brought up in https://github.com/javalin/javalin/issues/1020
Sounds good, I agree!
I'll write a short explanation of how https://github.com/javalin/javalin/pull/2068 works. The PR allows you to extend a `ContextPlugin` class, which has a `createExtension` method that you have to override. It would...
That's definitely a possibility, but won't be included in 6x. We have released a change similar to what was described above, you can read about it here: https://javalin.io/plugins/how-to#creating-a-plugin-with-config-and-extension You can...