Search Results for "separation"

...Minimal amount of boilerplate: no need to manually define a schema for every type in your API. Pure interface: errors and effects are returned explicitly (no exceptions thrown), all returned types are referentially transparent (no Future). Clean separation between schema definition and implementation: schema is defined and validated at compile time using Scala standard types, resolver (RootResolver) is a simple value provided at runtime. All interfaces are pure and types are referentially transparent. Schemas are type safe and derived at compile time. No need to manually define a schema for every type in your API. ...