It's in a very raw state, still, but it now compiles and runs. :tada:
In developing a Sangria example, I'm having difficulty in demonstrating even the most basic use of an SDL-based schema materialization. I'm getting
sangria.schema.SchemaMaterializationException: Can't extract value for a field 'User.id': not a map-like value.when I use an SDL file containing
type User {
id: Long!
name: String!
person: Person!
}I find it odd that ScalaInputUnmarshaller.isMapNode()is true only for Maps, not for case classes, or that my User case class doesn't get treated like a map. Wondering whether there's some linkage in the Scala code that I need.
The examples that I see tend to define the schema in Scala code. That has worked for me, but it obfuscates the schema's design. So it seems a real shame to do it that way.
Anyway, just mentioning the error for now, in case someone else has seen it. I'll have a clean example of the failure published soon.
InputObjectType is used to represent a GraphQL type that can be used as an input, for example for an argument.People usually use that with a scala case class as it's convenient. But you can use it with a trait, that you have to instantiate yourself at some point.
But if you are using a trait, we may have different implementations in scala. In that case, it may be better to expose a GraphQL interface and some concrete types of it.
2 replies
The modularization is in progress: the AST and the parser are now in separated modules.
Thanks @performantdata for this!
We add deprecations in the v2 releases to make the upgrading path easier. Make sure to fix those deprecations before upgrading.
Feedback welcome!
hi everybody! Could you please help me. I have graphql query and schema. What is the best way to analyze query and retrieve all requested fileds with proper type? For example in recursive structure:
sealed trait GraphQlFieldType {
val typeName: String
}
final case class GraphQlField(name: String, fieldType: GraphQlFieldType, isArray: Boolean = false)
final case class GraphQlFieldTypeDataClass(typeName: String,
fields: List[GraphQlField]) extends GraphQlFieldType
how do you handle transactions for subscriptions? For normal grahql requests I use a single transaction for queries and mutations. This transaction is part of the context. Using this same mechanism for subscriptions is insane. Do you create a separate
SubscriptionContext without transactions or do you guys have another suggestion?
Actions?
I have a use case where I accept multiple ids in a fetcher and want to return partial results in case fetcher couldn't give data for some of the IDs. For ex:
Schema : Car { id: int}
And let's say my input has 3 ids: 000,111,222 and out of those 2 were not found
I want response something like(basically to let the user know what happened with 2 ids which are not in data result):
"data": {
"getCar:[
{
"car": {
“id”: “111”
}
}
]
},
"errors": [
{
"message": “Couldn’t find data for car”
"code":"404"
“fields” : ”000,222”
}
]
}Is something like this possible in Sangria? Any help is greatly appreciated
2 replies
Suppose I have the following schema:
lazy val ParentType = ObjectType(
"Parent",
collect[...](
Public(
Field("child", ChildType,
resolve = _.value.child
)
)
)
)
lazy val ChildType = ObjectType(
"Child",
collect[...](
Public(
Field("something", StringType,
resolve = ...
)
)
)
)Is there a way to reference a field in the parent value/type within the resolve method of the ChildType's "something" resolve field.
I'm trying to do some custom instrumentation in New Relic similar to their recent graphql-java instrumentation:
https://github.com/newrelic/newrelic-java-agent/blob/5a035c11d3b0226655468d780c38342a60e790a7/instrumentation/graphql-java-16.2/src/main/java/com/nr/instrumentation/graphql/GraphQLSpanUtil.java#L39
What would be the equivalent of graphql-java's graphql.execution.ExecutionStrategyParameters? Can I derive it from sangria.ast.Document
https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/execution/ExecutionStrategyParameters.java
https://twitter.com/simon_yann/status/1499401657276252164
The only thing that is sort of holding me back: Scala 3 is out. It's shiney, new and much better than Scala 2.13. I saw that Sangria is not released for Scala 3 yet, correct?
Is there a timeline for this?
NoClassDefFoundError: sangria/parser/DeliveryScheme https://gist.github.com/jgillich/3e8d90dde7526d47a5f5fe496aae9889Source is very simple: https://github.com/graphql-crystal/benchmarks/tree/main/sangria
Any ideas? Wondering if it's related to sangria-akka-http-circe
can someone help me with the mutation?
Schema
implicit val inComercioType = deriveObjectType[DataRepo, comercio]()
val ComercioInObject = {
InputObjectType(
name = "Insert Comercio",
description = "",
List(
InputField(
name = "condicion",
fieldType = StringType),
InputField(
name = "laltitud",
fieldType = BigDecimalType),
InputField(
name = "longitud",
fieldType = BigDecimalType),
InputField(
name = "distancia",
fieldType = IntType),
)
)
}
val Condicion: Argument[String] = Argument("condicion", StringType)
val Latitud: Argument[BigDecimal] = Argument("latitud", BigDecimalType)
val Longitud: Argument[BigDecimal] = Argument("longitud", BigDecimalType)
val Distancia: Argument[Int] = Argument("distancia", IntType)
val MutationType =
ObjectType(
"Mutation",
fields[DataRepo, Unit](
Field(
name ="addComercios",
fieldType = ComercioOutObject,
arguments = Condicion :: Latitud :: Longitud :: Distancia :: Nil,
resolve = c => c.ctx.gqlAddComercios(c.arg(Condicion),c.arg(Latitud) ,c.arg(Longitud),c.arg(Distancia))
),
)
)
val SchemaDefinition: Schema[DataRepo, Unit] = Schema(QueryType,Some(MutationType))Datarepo
def gqlAddComercios(condicion: String,latitud:BigDecimal,longitud:BigDecimal,distancia:Int=250):List[getComercio] = comercio(condicion,latitud,longitud,distancia,token).insertContent
Hello,
I have the following field relation:
Field("setups",
fieldType = ListType(TransportSetup.toGraphType),
arguments = fetchTransportSetupArgs.createGraphTypeArgs,
resolve = ctx => setupFetcher.deferRelSeq(linkSetupByRouteId, ctx.value.getId)
),I would like to pass the arguments of the field to my fetcher, i tried to make work deferred resolver but no luck so far