From bbb76db83cc6d74604c97e4656f743f51a8f7c6a Mon Sep 17 00:00:00 2001 From: hochgi Date: Thu, 26 Dec 2024 21:24:38 +0200 Subject: [PATCH] rm mdoc:silent from sbt snippets as it does not compile on its own --- docs/reference/openapi-gen-sbt-plugin.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/openapi-gen-sbt-plugin.md b/docs/reference/openapi-gen-sbt-plugin.md index adb03b438..7af37bb7e 100644 --- a/docs/reference/openapi-gen-sbt-plugin.md +++ b/docs/reference/openapi-gen-sbt-plugin.md @@ -12,13 +12,13 @@ The plugin offers 2 modes of operation that can be mixed and used together: - Generating from managed dynamic OpenAPI spec files in `project/plugins.sbt` add the following line: -```scala mdoc:silent +```scala addSbtPlugin("dev.zio" % "zio-http-sbt-codegen" % "@VERSION@") // make sure the version of the sbt plugin // matches the version of zio-http you are using ``` in `build.sbt` enable the plugin by adding: -```scala mdoc:silent +```scala enablePlugins(ZioHttpCodegen) ``` @@ -34,7 +34,7 @@ or maybe you use services that expose OpenAPI specs via REST API, or perhaps you Whatever the scenario you're dealing with, it can be very handy to dynamically fetch/generate the latest most updated spec file, so the generated code stays up to date with any changes introduced. Here's how you can do it: -```scala mdoc:silent +```scala import gigahorse.support.apachehttp.Gigahorse import scala.concurrent.Await import scala.concurrent.duration.DurationInt @@ -61,7 +61,7 @@ ZIOpenApi / sourceGenerators += Def.task[Seq[File]] { ## Configuration The plugin offers a setting key which you can set to control how code is generated: -```scala mdoc:silent +```scala zioHttpCodegenConf := zio.http.gen.openapi.Config.default ```