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
Problem I want to solve is: I have a
@GraphQLField which takes a sealed trait as a Parameter. Now I want to create an InputObject which has every implementation of the sealed trait as a property and then create an alias which fails if not exactly one property is Some
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.
Currently getting an error when returning a large page of results Fetcher has not resolved non-optional ID ‘<SOME_ID>’
I’ve looked at the ids thrown by the error and found the objects/entities they refer to (it’s a nested object inside the object being queried) and they exist
I can do a more narrow query that filters for that specific object and get page with 1 result.
It so far only seems to blow up when I have to many.
Perhaps this is an issue with a the Future for the Field being queried is resolving before the defered resolver finishes?
I’ve been playing with page sizes all morning trying to reproduce but it looks like it’s related to the data.
I neglected to included the exception, it’s a
I neglected to included the exception, it’s a
sangria.execution.deferred.AbsentDeferredValueError
Since the thread trampolining removes the stacktrace
implicit def validatedType[A](
implicit lookup: GraphQLOutputTypeLookup[A]
): GraphQLOutputTypeLookup[Validated[A]] =
new GraphQLOutputTypeLookup[Validated[A]] {
def graphqlType: OutputType[Validated[A]] =
ObjectType(
s"Validated${lookup.graphqlType.namedType.name}",
fields[Ctx, Validated[A]](
Field("value", lookup.graphqlType, resolve = _.value.value),
Field(
"fatal",
ListType(FatalType),
resolve = _.value.status.fatal
),
Field(
"warning",
ListType(WarningType),
resolve = _.value.status.warning
)
)
)
}
The issue is having both a
Validated[String] and Validated[Option[String]]. If only one or the other is present, it works as expected ( in elm I get a Maybe String in the generated graphql object). But if both are present, only one is generated. So in my case, only a ValidatedString type exists, and its not a Maybe String in elm land.
Validated looks like this: case class Validated[A](value: A, status: Status) {
def map[B](f: A => B): Validated[B] =
copy(value = f(value))
}
I think it has something to do with how the type name is generated with this line:
s"Validated${lookup.graphqlType.namedType.name}",
so when both are present one overwrites the other and only one version is created.
and that is because
lookup.graphqlType.namedType reaches into option to get the wrapped type