Ktor 2.0: Should you apply @KtorDsl to a custom pl...

# ktor

[hfhbd]

Ktor 2.0: Should you apply @KtorDsl to a custom plugin? To the variable @KtorDsl val myPlugin = createRouteScopedPlugin("myPlugin, ::Config) {} AND to @KtorDsl class Config too?

[hfhbd]

If I apply the annotation, the implicit parameter does not work, and I need to add [e-mail] and [e-mail]...

[Aleksei Tirman [JB]]

@Rustam Siniukov

[Rustam Siniukov]

can you post a code snippet with example, please?

[hfhbd]

Sure, or the repo: https://github.com/hfhbd/RateLimit
https://github.com/hfhbd/RateLimit/blob/1bae93286ba56c113d3d4825dfe5cd4fecb22424/src/test/kotlin/app/softwork/ratelimit/RateLimitTest.kt#L84

[hfhbd]

@KtorDsl
val RateLimit = createRouteScopedPlugin("RateLimit, ::Config) {}

@KtorDsl
class Config

routing {
  get {
    call.respondText { "42" }
  }
  route("/login") {
    [e-mail](RateLimit) {
      [e-mail] {
        call.respondText { "/login called" }
      }
    }
  }
}

[Rustam Siniukov]

but KtorDsl has @Target(AnnotationTarget.CLASS, AnnotationTarget.TYPEALIAS, AnnotationTarget.TYPE, AnnotationTarget.FUNCTION)
you can’t apply it to val RateLimit = createRouteScopedPlugin("RateLimit, ::Config) {}

[hfhbd]

Oh, I simplified the sample too much. In my plugin, I used a function: @KtorDsl fun RateLimit(requiredParameter) = createRouteScopedPlugin(...). But in the end, install works without explicit this. But get does not.
At least the docs are wrong.