It would be even more awesome if all those classes...

# ktor

[Marc Knaup]

It would be even more awesome if all those classes would be interfaces, so that you can create a new interface that implements them by delegation. That would allow bringing many extensions in scope!

[Marc Knaup]

I guess that may not work that well due to excessive use of extension functions and nested DSL though 😕

[cy]

Well, from the classes, the only that don't have interface is Route. I see no reason to delegate it

[cy]

Could you please explain your usecase?

[Marc Knaup]

My DSL allows adding handlers to an existing route by accepting a Route.() -> Unit lambda.
I could use my own interface for defining handlers that take MyRoute.() -> Unit instead.

MyRoute has contextual properties and special contextual DSL.

[Marc Knaup]

Same for Application and PipelineContext (handlers).

I get some local state from the respective attributes and make it available through a nice DSL.

[cy]

These are interface and function

[cy]

(function is almost interface)

[cy]

Route is open so you may create your own implementations

[Marc Knaup]

I have to use Application for example because plenty of 1st and 3rd party modules add extension functions to it.

So I cannot use my own implementation and simply funnel everything to the Application behind the scenes.

I would have to replicate all extension functions of all possible Ktor features/libraries.

[Marc Knaup]

Basically what I’m building is another layer on top of Ktor that wires together modular configuration with Kodein + [Ktor] + [MongoDB] + [GraphQL].

So I have one DSL over everything and specific integrations for each “module” like Ktor.
Making them work nicely together isn’t the easiest task :)