sandorbedo

sandorbedo

Hi,

Is it possible to access the original GraphQL query document (as a string) from a resolver function?

The resolution struct contains all information needed to reconstruct the query but it would be simpler to just use the one the client submitted.

Showing Posts 1 to 3

benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

Hi @sandorbedo can you elaborate regarding your use case?

sandorbedo

sandorbedo OP

Sure.

In order to generate a reply for some of the queries in my app, I need to connect to another GraphQL server and forward/proxy the original query. Right now I build the query document up from the resolution struct, which is error prone.

a) It would be great to have a function in absinthe that converts the resolution into the query document.

b) Another solution I was thinking about is to use a plug early in the plug chain, that takes the original query document out and saves it somewhere. THis has two downsides: 1) since I have no abbess to the Plug.Conn struct, it’s hard to figure out where to save tha query string. Another problem is that it would be difficult to do for all the possible input methods (the documents coming from playground Absinthe.Plug.GraphiQL, the normal HTTP POST based Absinthe.Plag queries and the websocket based ones from Absinthe.GraphqlWS).

So basically the question is: how can I get the original query document in the resolver? This is needed to forward it to another GraphQL server based on certain conditions.

maartenvanvliet

maartenvanvliet

During document execution an intermediate representation of the document is available in the Absinthe.Blueprint struct, specifically the input. This represantation supports the Inspect protocol so it can be converted back to the string representation using inspect(blueprint.input, pretty: true).

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

webofbits
Cairn is a small OTP library for message delivery, lightweight function processes, supervised work, and waiting on results. The goal is ...
New
GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews