Hey folks! After having worked with Sangria in a previous project at another company, I'm now looking to build a GraphQL API at the startup I'm now working for. Naturally, Sangria is an enticing option.
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?
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?
Trying to update sangria to 3.0 and I get a
Source is very simple: https://github.com/graphql-crystal/benchmarks/tree/main/sangria
Any ideas? Wondering if it's related to sangria-akka-http-circe
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
@DandyDev for scala 3, there's still one big dependency that needs to be cross-compiled, with a lot of macros: https://github.com/sangria-graphql/sangria/projects/2
1 reply
@DevFlex we're using projector but we are using the graphql field names to know which fields to fetch from mongo. I'm not sure what you are trying to achieve. Can you explain further?
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
i can only pass ID
what am i doing wrong?
Sangria is not ready for scala 3 yet. There's still one big dependency that needs to be cross-compiled, with a lot of macros: https://github.com/sangria-graphql/sangria/projects/2
Any help welcome here ;)
Any help welcome here ;)
@lukasz-swider A Fetcher defines the type of the
If you need more control, you can go lower level, and use
In my company, we are using both, and we combine them with
ID. You can define it to what type you need.If you need more control, you can go lower level, and use
DeferredValueand DeferredResolver.In my company, we are using both, and we combine them with
DeferredResolver.fetchersWithFallback.
As I understand it: if you have n different values from n branches, this method is used to know what to do with those n values.
For example, in the MeasureComplexity:
def reduceAlternatives(alternatives: Seq[Acc]) = alternatives.maxIn TagCollector, we collect all tags:
def reduceAlternatives(alternatives: Seq[Acc]) = alternatives.toVector.flatten
Does this help?
I've been trying to dig into Sangria Fetchers (Data Loaders) and couldn't quite figure out if they go across requests or if they only act per-request. I found this PR mentioning that the caching is per-request, but haven't found anything to confirm if the batching/data loader part is as well 🤔 sangria-graphql/sangria#447
For example, imagine this scenario:
- Request A: Get ID 2 via Fetcher
- Request B: Get ID 2 via Fetcher
Would this result in 1 database calls (so, it works across requests) or 2 database calls (it's per-request)?
query{
profession(id: "123456"){
resultList{
name
description
professionType
address
email
engineer(domain : "Software",skill: "Scala"){
department
domain
country
skills
}
doctor(speciality: "Ortho"){
hospital
speciality
yearsOfExperience
}
}
}
}
profession(id: "123456"){
resultList{
name
description
professionType
address
engineer(domain : "Software",skill: "Scala"){
department
domain
country
skills
}
doctor(speciality: "Ortho"){
hospital
speciality
yearsOfExperience
}
}
}
}
I have this query . And I want to fetch the arguments of sub-fields example - engineer field argument - domain
is it possible using sangria
as I want to query for professions under given with engineer skill as scala
@puneettandon please try to format your post, it will help the readability.
Yes, it's possible to have arguments on any field.
Example:
Yes, it's possible to have arguments on any field.
Example:
Field(
"field_name",
arguments = IncludeKeys :: ExcludeKeys :: Limit :: Offset :: SortArg :: Nil,
resolve = ctx => {
val includes = ctx.arg(IncludeKeys)
val excludes = ctx.arg(ExcludeKeys)
val limit = ctx.arg(Limit)
val offset = ctx.arg(Offset)
Hi ..I am new to sangaria graphql. I have a big list (about 500) of map having more than 300 key ,values in each map. I noticed while resolving , it is taking a lot of time approx 800-1200 ms . Can I improve the performance . Is there any way I can make the resolution of list parallelly. Any help highly appreciated.
My app is currently entirely Scala 2.13, so I'd have to carve out a chunk of time, but this was the last piece I was waiting for.
I'm trying to make a HandledException and include a custom JSON response. That goes through the additionalFields: Map[String, ResultMarshaller#Node] = Map.empty, field, which Node appears to be an interface, perhaps supporting other libraries (ex: io.circe.Json).
Is there a way I can somehow pass Json directly into the HandledException.additionalFields ?
Hah, I think I figured it out, I just needed the right implicit conversion.
import _root_.sangria.marshalling.circe._
val params = Map[String, ResultMarshaller#Node]("" -> io.circe.Json.obj())
HandledException(
log.traceId,
params,
addFieldsInError = true,
addFieldsInExtensions = false,
)
So, this actually works. A little messy, but I only need this code in one place.
import _root_.sangria.marshalling.circe._
val json: CirceResultMarshaller.Node = Json.obj(???)
val params: Map[String, ResultMarshaller#Node] = Map[String, ResultMarshaller#Node](
"error" -> json
)
HandledException(
log.traceId,
params,
addFieldsInError = true,
addFieldsInExtensions = false,
)