Hey guys. We writing shared queries to be used by ...

# apollo-kotlin

[Vitaliy Kondratiev]

Hey guys. We writing shared queries to be used by two clients. This means that a lot of usage of directives. My question is, is there a way to have all apollo clients attach a directive for a queries/mutations/subscriptions? Or do we have to make sure that all of our Queries provide that argument?

[bod]

Hi!
Maybe you could automatically manipulate / process your operations before they are sent to the backend, with an ApolloInterceptor?

[mbonnin]

Would you have an example of such a directive? Typically directives are part of the query but are not really passed as arguments. They're just "part of the query"

[Vitaliy Kondratiev]

We have 2 apps that share graphql operation with some slight differences that we use directives to define. One app will always have the value be false and another will always have the value be true. Although we can add it to almost every query that would need it I'm wondering if there is a way to do it in a generic way.

query Meta() {
    ... SomeFragment
}

fragment SomeFragment on Whatever {
    attribute1 @include(if: $isApp1)
    attribute2 @skip(if: $isApp1)
}

this case is simple but imagine that SomeFragment is a super common fragment is used almost everywhere

[mbonnin]

Gotcha. You could transform the query on the fly like @bod was suggesting. It'll require making sure that you don't add a variable if it's never used because GraphQL is very strict about unused variables and will most likely error if that happens

[Vitaliy Kondratiev]

how do I go about doing that? I couldn't figure out with ApolloInterceptor

[Vitaliy Kondratiev]

we are on 2.5.11 currently

[mbonnin]

I was going to say implementing your custom HttpRequestComposer might work. But that's not in 2.x

[Vitaliy Kondratiev]

I tried last night using an OkHttp interceptor. And could actually add a variable to the body but then kept getting this from the server

"message": "Variable \"isTsb\" is not defined by operation \"StartupQuery\"."

[mbonnin]

Yep, you'll need to add it to the query document as well:

query Meta($isApp1: Boolean!, $isApp2: Boolean!)

[Vitaliy Kondratiev]

ugh but with Persisted Queries it will break right?

[mbonnin]

The trick is not adding it if none of isApp1 or isApp2 is used

[mbonnin]

Auto Persisted Queries will be fine

[Vitaliy Kondratiev]

we don't have auto PQs

[Vitaliy Kondratiev]

sounds tricky af maybe it's more simple to just add it to all operations 🤷

[mbonnin]

If you're using something like Apollo safelisting or using OperationOutput to register your ids then indeed modifying the query document at runtime will break

[mbonnin]

Depends the number of operations you have

[mbonnin]

Another way to look at this would be to define a "pre-processing" Gradle task that automatically modifies the queries

[mbonnin]

Because it's compile-time, it'll work with safelisting or other whitelisting mecanisms