RequestEntitySyntax
class Object
trait Matchable
class Any
Value members
Concrete methods
Alternative between two possible request entities, differentiated by the
Content-Type
header
Alternative between two possible request entities, differentiated by the
Content-Type
header
- Note:
If
A
andB
are both JSON-encoded and use disjoint schemas, use endpoints4s.algebra.JsonSchemas.TaggedOps#orElse at the schema level instead- Server interpreters accept either of the request entities
- Client interpreters provide one of the two request entities
- Documentation interpreters list all possible content types and their entities