private def builder: ResolverBasedAstSchemaBuilder[UserContext] =
AstSchemaBuilder.resolverBased[UserContext](
riFieldResolver.resolvers :+ FieldResolver.defaultInput[UserContext, JsValue]: _*
)
private val schemaString = Source.fromResource("schema.graphql").mkString
private val schemaAst = QueryParser.parse(schemaString).get
val schema: Schema[UserContext, Any] = Schema.buildFromAst(schemaAst, builder.validateSchemaWithException(schemaAst)) private val riThreadResolver = FieldResolver[UserContext] {
case (TypeName("Subscription"), FieldName("fi_thread")) =>
Field.subs("allEvents", null, resolve = { _: Context[UserContext, _] =>
Source(1 to 10)
.map { _ =>
s"""{
"data": {
"fi_thread": "${LocalTime.now().toString}",
"fi_thread2": "${LocalTime.now().toString}"
}
}"""
}
.map(Action(_))
}).resolve
} private[sangria] case class SubscriptionValue[Ctx, Val, S[_]](source: Val, stream: SubscriptionStream[S]) extends LeafAction[Ctx, Val] {
override def map[NewVal](fn: Val => NewVal)(implicit ec: ExecutionContext): SubscriptionValue[Ctx, NewVal, S] =
throw new IllegalStateException("`map` is not supported subscription actions. Action is only intended for internal use.")
} this is probably useful implicit but it's private
If I am SUPERRRR honest, I can't stand all of these nested objects as is, and simply taking these objects and flattening them out also behaves as expected. I am however, fascinated by the behavior. I still am convinced this is a Scala semantics thing that is way over my head. But I am happy to keep seeing if I can find what is happening.
Current hunch is: https://github.com/sangria-graphql/sangria/blob/master/modules/core/src/main/scala/sangria/schema/Schema.scala#L890-L893, those lazy vals are used in the coercions. Running some tests as we speak
NOPE! Alright and with that I am tapping out on this one. Please re-organize all of your code :P
Regarding the switching left / right hand comparison, the reason that works is that it forces coercion. I have never looked deeply into what all goes on behind the scenes in sangria, so maybe it's time. As I looked deeper, it looks like the nullability come from a
A <: Null type constraint, and that's deep in Tree (part of the Ast code) That said... I am currently fully unqualified to fix any of this, but I would encourage you to fix it in user land at the moment (a small re-organization), but I'll see if I can get some failing test cases added and maybe someone could look deeper
Can anyone point me to an example of implementing a filter on a subscription? I would like a user to be able to subscribe to project update events using something like
projectUpdated(projectId: "someProjectId") where only events with an id matching the subscribed projectId are returned to the subscriber.
@danielbussone about subscription (https://sangria-graphql.github.io/learn/#stream-based-subscriptions): in the resolve function, you can access the arguments to push only desired events I think.
But PartialFutureValue won’t compile
val Food: Field[Context, Val] = {
Field(
name = “Food",
fieldType = OptionType(StringType),
resolve = _ => PartialFutureValue(Future.successful(PartialValue(Some("Waffles"), Vector(new Exception("Pancakes”)))))
)
}There’s type mismatch, it’s looking for sangria.schema.Action[Any,Option[String]]
and just refuse the request by whatever mechanism (like throw an exception or returns a Forbidden)
Hi folks. I have a question about sangria marshalling. I am playing around with attempting to make a marshaller which marshals results to Thrift, but one sticking point is that it appears that ResultMarshaller (https://github.com/sangria-graphql/sangria-marshalling-api/blob/master/src/main/scala/sangria/marshalling/ResultMarshaller.scala) does not hint at which arm of a union is being marshalled, thus I cannot seem to figure out how to render a more refined type other than key/value pairs. Does anyone have any ideas for how I could attempt to solve for this?
1 reply
Hey, wanting to implement pagination in the plural GQL queries. Does anybody know if it's already part of the Sangria lib or can anybody point me to a resource about how to implement it.
Have read this:
https://graphql.org/learn/pagination/
and following their advice i would like to implement cursor based pagination
Have read this:
https://graphql.org/learn/pagination/
and following their advice i would like to implement cursor based pagination
Basically, same as you would if it was a simple REST service
to somehow emulate a Union/Interface
I'm also not sure if I can write the mapping of InputFields to Scala class by hand somehow? There seems to be a lot of macro / reflection magic involved here?
At least I think... it compiles so far lets say :P
so anyway to create an Input type by mapping an already existing InputType? Or by doing the deserialization myself (e.g. MyClass(arg("a"), arg("b")))
I thought the FromInput stuff is happening "somehow" in InputObject... so with these 2 combined I can write my own deserialization, nice!
hey guys, need your advice:
switched sangria to 2.1.0
PR looks like this
"org.sangria-graphql" %% "sangria" % "1.4.2" => "2.1.0",
"org.sangria-graphql" %% "sangria-relay" % "1.4.2" => "2.1.0",
"org.sangria-graphql" %% "sangria-circe" % "1.2.1" => "1.3.1",
"org.sangria-graphql" %% "sangria-slowlog" % "0.1.8" => "2.0.1",nothing else was changed.
And faced a memory leak 6 hours after the update (maybe related to traffic).
Maybe someone also faced mem leak at sangria 2.10 ?
running with this version since months with high traffic, and we have no memory leak about it.
But the leak could also come from how you instantiate your schema...
The better to find it is to check the memory, for example with java mission control. Altough I don't know which tools will work with graalvm.
But the leak could also come from how you instantiate your schema...
The better to find it is to check the memory, for example with java mission control. Altough I don't know which tools will work with graalvm.
Hey! I want to write a graphql mutation using sangria which returns a List. However, currently I only can figure out writing mutations which return an object not a list of objects. Like :- val MutationType: ObjectType[GraphQLContext, Unit] = ObjectType("Mutation", fields[GraphQLContext, Unit](
And then val schema: Schema[GraphQLContext, Unit] = Schema(QueryType, Some(MutationType))
Hi, I have a question about deferred resolution. Is there a way to run multiple deferred resolutions one by one? What I want to achieve in resolver function is:
for {
idsA <- deferredFetchA
idsB <- deferredFetchB
selectedItems <- do sth with idsA and idsB
} yield anotherDeferredFetch(selectedItems)I was trying to play with DeferredValue(...) but with no success
See https://sangria-graphql.github.io/learn/#deferred-value-resolution
In your schema, use your own class that extends
In your
In your schema, use your own class that extends
Deferred.In your
DeferredResolver, you have access to all your accumulated Deferred instances. Based on this input, you can choose how to resolve them. And this can be one by one if you want to.
If you use
This PR would need help (rebase on last version I guess) so that it could be integrated.
Fetcher, you might be interested in this change that allows setting the max concurrency: https://github.com/sangria-graphql/sangria/pull/454/filesThis PR would need help (rebase on last version I guess) so that it could be integrated.