Release 1.9.7

README.md

@@ -131,7 +131,7 @@ tapir documentation is available at [tapir.softwaremill.com](http://tapir.softwa
 Add the following dependency:
 
 ```sbt
-"com.softwaremill.sttp.tapir" %% "tapir-core" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-core" % "1.9.7"
 ```
 
 Then, import:

generated-doc/out/client/http4s.md

@@ -3,7 +3,7 @@
 Add the dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-http4s-client" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-http4s-client" % "1.9.7"
 ```
 
 To interpret an endpoint definition as an `org.http4s.Request[F]`, import:

generated-doc/out/client/play.md

@@ -6,13 +6,13 @@ See the [Play framework documentation](https://www.playframework.com/documentati
 For **Play 3.0**, add the dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-play-client" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-play-client" % "1.9.7"
 ```
 
 For **Play 2.9**, add
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-play29-client" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-play29-client" % "1.9.7"
 ```
 
 instead. Furthermore, replace all uses of `sttp.capabilities.pekko.PekkoStreams` in the following code snippets with `sttp.capabilities.akka.AkkaStreams`.

generated-doc/out/client/sttp.md

@@ -3,7 +3,7 @@
 Add the dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-sttp-client" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-sttp-client" % "1.9.7"
 ```
 
 To make requests using an endpoint definition using the [sttp client](https://github.com/softwaremill/sttp), import:
@@ -100,7 +100,7 @@ In this case add the following dependencies (note the [`%%%`](https://www.scala-
 instead of the usual `%%`):
 
 ```scala
-"com.softwaremill.sttp.tapir" %%% "tapir-sttp-client" % "1.9.6"
+"com.softwaremill.sttp.tapir" %%% "tapir-sttp-client" % "1.9.7"
 "io.github.cquiroz" %%% "scala-java-time" % "2.2.0" // implementations of java.time classes for Scala.JS
 ```
 

generated-doc/out/docs/asyncapi.md

@@ -3,7 +3,7 @@
 To use, add the following dependencies:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-asyncapi-docs" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-asyncapi-docs" % "1.9.7"
 "com.softwaremill.sttp.apispec" %% "asyncapi-circe-yaml" % "..." // see https://github.com/softwaremill/sttp-apispec
 ```
 

generated-doc/out/docs/json-schema.md

@@ -3,7 +3,7 @@
 You can conveniently generate JSON schema from Tapir schema, which can be derived from your Scala types. Use `TapirSchemaToJsonSchema`:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-apispec-docs" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-apispec-docs" % "1.9.7"
 ```
 
 Schema generation can now be performed like in the following example:
@@ -18,7 +18,7 @@ import sttp.tapir.generic.auto._
     case class Child(age: Int, height: Option[Int])
   }
   case class Parent(innerChildField: Child, childDetails: Childhood.Child)
-  case class Child(childName: String) // to illustrate unique name generation // to illustrate unique name generation
+  case class Child(childName: String) // to illustrate unique name generation
   val tSchema = implicitly[Schema[Parent]]
 
   val jsonSchema: ASchema = TapirSchemaToJsonSchema(

generated-doc/out/docs/openapi.md

@@ -13,7 +13,7 @@ these steps can be done separately, giving you complete control over the process
 To generate OpenAPI documentation and expose it using the Swagger UI in a single step, first add the dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-swagger-ui-bundle" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-swagger-ui-bundle" % "1.9.7"
 ```
 
 Then, you can interpret a list of endpoints using `SwaggerInterpreter`. The result will be a list of file-serving 
@@ -55,7 +55,7 @@ for details.
 Similarly as above, you'll need the following dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-redoc-bundle" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-redoc-bundle" % "1.9.7"
 ```
 
 And the server endpoints can be generated using the `sttp.tapir.redoc.bundle.RedocInterpreter` class.
@@ -65,7 +65,7 @@ And the server endpoints can be generated using the `sttp.tapir.redoc.bundle.Red
 To generate the docs in the OpenAPI yaml format, add the following dependencies:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-openapi-docs" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-openapi-docs" % "1.9.7"
 "com.softwaremill.sttp.apispec" %% "openapi-circe-yaml" % "..." // see https://github.com/softwaremill/sttp-apispec
 ```
 
@@ -133,22 +133,22 @@ For example, generating the OpenAPI 3.0.3 YAML string can be achieved by perform
 
 Firstly add dependencies:
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-openapi-docs" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-openapi-docs" % "1.9.7"
 "com.softwaremill.sttp.apispec" %% "openapi-circe-yaml" % "..." // see https://github.com/softwaremill/sttp-apispec
 ```
 
 and generate the documentation by importing valid extension methods and explicitly specifying the "3.0.3" version in the OpenAPI model:
 ```scala
 import sttp.apispec.openapi.OpenAPI
-import sttp.apispec.openapi.circe.yaml._ // for `toYaml` extension method // for `toYaml` extension method
+import sttp.apispec.openapi.circe.yaml._ // for `toYaml` extension method
 import sttp.tapir._
 import sttp.tapir.docs.openapi.OpenAPIDocsInterpreter
 
 case class Book(id: Option[Long], title: Option[String])
 
 val booksListing = endpoint.in(path[String]("bookId"))
 
-val docs: OpenAPI = OpenAPIDocsInterpreter().toOpenAPI(booksListing, "My Bookshop", "1.0").openapi("3.0.3") // "3.0.3" version explicitly specified // "3.0.3" version explicitly specified
+val docs: OpenAPI = OpenAPIDocsInterpreter().toOpenAPI(booksListing, "My Bookshop", "1.0").openapi("3.0.3") // "3.0.3" version explicitly specified
 
 println(docs.toYaml3_0_3) // OpenApi 3.0.3 YAML string would be printed to the console
 ```
@@ -163,12 +163,12 @@ The modules `tapir-swagger-ui` and `tapir-redoc` contain server endpoint definit
 yaml format, will expose it using the given context path. To use, add as a dependency either
 `tapir-swagger-ui`:
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-swagger-ui" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-swagger-ui" % "1.9.7"
 ```
 
 or `tapir-redoc`:
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-redoc" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-redoc" % "1.9.7"
 ```
 
 Then, you'll need to pass the server endpoints to your server interpreter. For example, using akka-http:
@@ -264,7 +264,7 @@ val alternativeAuthEndpoint = endpoint.securityIn(
       case Left(oldToken)  => (Some(oldToken), None)
       case Right(newToken) => (None, Some(newToken))
     }
- )        
+ )    
 
 val alternativeOptionalAuthEndpoint = alternativeAuthEndpoint.securityIn(emptyAuth)
 ```

generated-doc/out/endpoint/integrations.md

@@ -14,7 +14,7 @@ The `tapir-cats` module contains additional instances for some [cats](https://ty
 datatypes as well as additional syntax:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-cats" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-cats" % "1.9.7"
 ```
 
 - `import sttp.tapir.integ.cats.codec._` - brings schema, validator and codec instances
@@ -24,7 +24,7 @@ Additionally, the `tapir-cats-effect` module contains an implementation of the `
 between the sttp-internal `MonadError` and the cats-effect `Sync` typeclass:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-cats-effect" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-cats-effect" % "1.9.7"
 ```
 
 ## Refined integration
@@ -33,7 +33,7 @@ If you use [refined](https://github.com/fthomas/refined), the `tapir-refined` mo
 validators for `T Refined P` as long as a codec for `T` already exists:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-refined" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-refined" % "1.9.7"
 ```
 
 You'll need to extend the `sttp.tapir.codec.refined.TapirCodecRefined`
@@ -54,7 +54,7 @@ If you use [iron](https://github.com/Iltotore/iron), the `tapir-iron` module wil
 validators for `T :| P` as long as a codec for `T` already exists:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-iron" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-iron" % "1.9.7"
 ```
 
 The module is only available for Scala 3 since iron is not designed to work with Scala 2.
@@ -146,7 +146,7 @@ The `tapir-enumeratum` module provides schemas, validators and codecs for [Enume
 enumerations. To use, add the following dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-enumeratum" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-enumeratum" % "1.9.7"
 ```
 
 Then, `import sttp.tapir.codec.enumeratum._`, or extends the `sttp.tapir.codec.enumeratum.TapirCodecEnumeratum` trait.
@@ -159,7 +159,7 @@ If you use [scala-newtype](https://github.com/estatico/scala-newtype), the `tapi
 schemas for types with a `@newtype` and `@newsubtype` annotations as long as a codec and schema for its underlying value already exists:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-newtype" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-newtype" % "1.9.7"
 ```
 
 Then, `import sttp.tapir.codec.newtype._`, or extend the `sttp.tapir.codec.newtype.TapirCodecNewType` trait to bring the implicit values into scope.
@@ -170,7 +170,7 @@ If you use [monix newtypes](https://github.com/monix/newtypes), the `tapir-monix
 schemas for types which extend `NewtypeWrapped` and `NewsubtypeWrapped` annotations as long as a codec and schema for its underlying value already exists:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-monix-newtype" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-monix-newtype" % "1.9.7"
 ```
 
 Then, `import sttp.tapir.codec.monix.newtype._`, or extend the `sttp.tapir.codec.monix.newtype.TapirCodecMonixNewType` trait to bring the implicit values into scope.
@@ -181,7 +181,7 @@ If you use [ZIO Prelude Newtypes](https://zio.github.io/zio-prelude/docs/newtype
 schemas for types defined using `Newtype` and `Subtype` as long as a codec and a schema for the underlying type already exists:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-zio-prelude" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-zio-prelude" % "1.9.7"
 ```
 
 Then, mix in `sttp.tapir.codec.zio.prelude.newtype.TapirNewtypeSupport` into your newtype to bring the implicit values into scope:
@@ -220,7 +220,7 @@ For details refer to [derevo documentation](https://github.com/tofu-tf/derevo#in
 To use, add the following dependency:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-derevo" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-derevo" % "1.9.7"
 ```
 
 Then you can derive schema for your ADT along with other typeclasses besides ADT declaration itself:

generated-doc/out/endpoint/json.md

@@ -52,7 +52,7 @@ stringJsonBody.schema(implicitly[Schema[MyBody]].as[String])
 To use [Circe](https://github.com/circe/circe), add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-circe" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-circe" % "1.9.7"
 ```
 
 Next, import the package (or extend the `TapirJsonCirce` trait, see [MyTapir](../mytapir.md)):
@@ -125,7 +125,7 @@ Now the above JSON object will render as
 To use [µPickle](http://www.lihaoyi.com/upickle/) add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-upickle" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-upickle" % "1.9.7"
 ```
 
 Next, import the package (or extend the `TapirJsonuPickle` trait, see [MyTapir](../mytapir.md) and add `TapirJsonuPickle` not `TapirCirceJson`):
@@ -160,13 +160,13 @@ For more examples, including making a custom encoder/decoder, see [TapirJsonuPic
 To use [Play JSON](https://github.com/playframework/play-json) for **Play 3.0**, add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-play" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-play" % "1.9.7"
 ```
 
 For **Play 2.9** use:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-play29" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-play29" % "1.9.7"
 ```
 
 Next, import the package (or extend the `TapirJsonPlay` trait, see [MyTapir](../mytapir.md) and add `TapirJsonPlay` not `TapirCirceJson`):
@@ -182,7 +182,7 @@ Play JSON requires `Reads` and `Writes` implicit values in scope for each type y
 To use [Spray JSON](https://github.com/spray/spray-json) add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-spray" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-spray" % "1.9.7"
 ```
 
 Next, import the package (or extend the `TapirJsonSpray` trait, see [MyTapir](../mytapir.md) and add `TapirJsonSpray` not `TapirCirceJson`):
@@ -198,7 +198,7 @@ Spray JSON requires a `JsonFormat` implicit value in scope for each type you wan
 To use [Tethys JSON](https://github.com/tethys-json/tethys) add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-tethys" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-tethys" % "1.9.7"
 ```
 
 Next, import the package (or extend the `TapirJsonTethys` trait, see [MyTapir](../mytapir.md) and add `TapirJsonTethys` not `TapirCirceJson`):
@@ -214,7 +214,7 @@ Tethys JSON requires `JsonReader` and `JsonWriter` implicit values in scope for
 To use [Jsoniter-scala](https://github.com/plokhotnyuk/jsoniter-scala) add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-jsoniter-scala" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-jsoniter-scala" % "1.9.7"
 ```
 
 Next, import the package (or extend the `TapirJsonJsoniter` trait, see [MyTapir](../mytapir.md) and add `TapirJsonJsoniter` not `TapirCirceJson`):
@@ -230,7 +230,7 @@ Jsoniter Scala requires `JsonValueCodec` implicit value in scope for each type y
 To use [json4s](https://github.com/json4s/json4s) add the following dependencies to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-json4s" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-json4s" % "1.9.7"
 ```
 
 And one of the implementations:
@@ -261,7 +261,7 @@ implicit val formats: Formats = org.json4s.jackson.Serialization.formats(NoTypeH
 To use [zio-json](https://github.com/zio/zio-json), add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-zio" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-zio" % "1.9.7"
 ```
 Next, import the package (or extend the `TapirJsonZio` trait, see [MyTapir](../mytapir.md) and add `TapirJsonZio` instead of `TapirCirceJson`):
 

generated-doc/out/endpoint/oneof.md

@@ -197,7 +197,7 @@ implicit val userXmlCodec: Codec[String, User, CodecFormat.Xml] =
     .mapDecode { xml =>
       DecodeResult.fromOption("""<name>(.*?)</name>""".r.findFirstMatchIn(xml).map(_.group(1)).map(User))
     }(user => s"<name>${user.name}</name>")
-    .schema(implicitly[Schema[User]])          
+    .schema(implicitly[Schema[User]])     
 
 oneOfBody(
   jsonBody[User],

generated-doc/out/endpoint/pickler.md

@@ -9,7 +9,7 @@ In [other](json.md) tapir-JSON integrations, you have to keep the `Schema` (whic
 To use pickler, add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-json-pickler" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-json-pickler" % "1.9.7"
 ```
 
 Please note that it is available only for Scala 3 and Scala.JS 3.

generated-doc/out/endpoint/schemas.md

@@ -81,7 +81,9 @@ integration layer.
 
 This method may be used both with automatic and semi-automatic derivation. 
 
-## Derivation for recursive types in Scala3
+## Scala3-specific derivation
+
+### Derivation for recursive types
 
 In Scala3, any schemas for recursive types need to be provided as typed `implicit def` (not a `given`)!
 For example:
@@ -96,6 +98,25 @@ object RecursiveTest {
 The implicit doesn't have to be defined in the companion object, just anywhere in scope. This applies to cases where
 the schema is looked up implicitly, e.g. for `jsonBody`.
 
+### Derivation for union types
+
+Schemas for union types must be declared by hand, using the `Schema.derivedUnion[T]` method. Schemas for all components
+of the union type must be available in the implicit scope at the point of invocation. For example:
+
+```scala
+val s: Schema[String | Int] = Schema.derivedUnion
+```
+
+If the union type is a named alias, the type needs to be provided explicitly, e.g.:
+
+```scala
+type StringOrInt = String | Int
+val s: Schema[StringOrInt] = Schema.derivedUnion[StringOrInt]
+```
+
+If any of the components of the union type is a generic type, any of its validations will be skipped when validating
+the union type, as it's not possible to generate a runtime check for the generic type.
+
 ## Configuring derivation
 
 It is possible to configure Magnolia's automatic derivation to use `snake_case`, `kebab-case` or a custom field naming

generated-doc/out/endpoint/static.md

@@ -12,7 +12,7 @@ from local files or application resources. These endpoints respect etags, byte r
 In order to use static content endpoints, add the module to your dependencies:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-files" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-files" % "1.9.7"
 ```
 
 ## Files

generated-doc/out/generator/sbt-openapi-codegen.md

@@ -11,7 +11,7 @@
 Add the sbt plugin to the `project/plugins.sbt`:
 
 ```scala
-addSbtPlugin("com.softwaremill.sttp.tapir" % "sbt-openapi-codegen" % "1.9.6")
+addSbtPlugin("com.softwaremill.sttp.tapir" % "sbt-openapi-codegen" % "1.9.7")
 ```
 
 Enable the plugin for your project in the `build.sbt`:

generated-doc/out/quickstart.md

@@ -3,7 +3,7 @@
 To use tapir, add the following dependency to your project:
 
 ```scala
-"com.softwaremill.sttp.tapir" %% "tapir-core" % "1.9.6"
+"com.softwaremill.sttp.tapir" %% "tapir-core" % "1.9.7"
 ```
 
 This will import only the core classes needed to create endpoint descriptions. To generate a server or a client, you