Type-safe client: custom factory / supplier?

[jmini]

I am still working with the client and the query defined here #2224 (comment)

I would like to test a modification in InlineFragmentImpl and I was wondering if I can do this from the outside (from my Java main or Quarkus app)

I have seen the part that creates the GraphQL query seems to be based on the concept of Factory / Supplier:

smallrye-graphql/client/api/src/main/java/io/smallrye/graphql/client/core/factory/InlineFragmentFactory.java

Lines 7 to 8 in 7a7a3ab

	public interface InlineFragmentFactory extends Supplier<InlineFragment> {
	}

But I couldn't find if I can register my own supplier or not.

[jmini]

Maybe what I wrote does not make sense InlineFragmentImpl seems to be used in the dynamic client.

I continue my investigation on how I can influence the query generation of the typesafe client

[jmini]

The logic seems to be in io.smallrye.graphql.client.impl.typesafe.QueryBuilder and this might be very difficult to customize…

[jmartisk]

So what exactly do you need to customize about the inline fragment?

[jmini]

I have opened a PR to discuss my precise problem and requested change:
#2264

If you know how I can try this change in my quarkus-app and/or in my standalone java app (executed using Jbang) I would be really interested.

[jmini]

@jmartisk how realistic is for me to build a custom smallrye-graphql containing my fix and a custom quarkus build with the same fix. I fear it is almost impossible.

---

What I have is that if I build locally smallrye-graphql, the client works as expected.

Client model version:
unblu/gitlab-workitem-graphql-client@556ac6f

And this implementation:

io.smallrye:smallrye-graphql-client-implementation-vertx:2.12.2-SNAPSHOT

Containing my improvement discussed in #2264

So instead of using a 2.12.2-SNAPSHOT I could create a release somewhere (our company nexus or something) and use that version.

---

But then to have this running in Quarkus? What should I do?

I already tried some crazy things in the past to force quarkus to use a newer smallrye-graphql` version:
quarkusio/quarkus#43756 (comment)
(but I am not really sure it really ever worked)

As a work-around is there a way to tell Quarkus to not use the build-steps and do everything at runtime?

---

My only other idea to have this fixed ASAP is to abandon the type-safe client and to transform it into a dynamic client where I would control the query.

[jmartisk]

You can simply build a custom snapshot of smallrye-graphql and then, in the application's pom, declare io.smallrye:smallrye-graphql-client-parent as a separate dependency with the version pointing at your snapshot. AFAIK that should override the version from Quarkus. You may need to put it before the io.quarkus:quarkus-smallrye-graphql-client so that it has more priority (I think)

[jmartisk]

If it doesn't work, you can checkout the quarkus main branch, change the version of smallrye-graphql dependency in bom/application/pom.xml and build a snapshot of Quarkus that depends on your snapshot of smallrye-graphql. That works for sure.

[jmini]

Thank you for those input. I will give it a try

[jmini]

in the application's pom, declare io.smallrye:smallrye-graphql-client-parent as a separate dependency with the version pointing at your snapshot. AFAIK that should override the version from Quarkus.

I think this is a maven thing.

My release (the maven release process failed somewhere but the client jars were published and I could upload them to our company maven repo) is based on this tag:
https://github.com/unblu/smallrye-graphql/releases/tag/2.12.2-unblu-2

With Gradle I did this:

    //upgrade 'smallrye-graphql-*' projects.
    configurations.all {
        resolutionStrategy.eachDependency { DependencyResolveDetails details ->
            if (details.requested.group == 'io.smallrye' && details.requested.name.startsWith('smallrye-graphql') && details.requested.version == '2.12.1') {
                details.useTarget group: 'patched.unblu.io.smallrye', name: details.requested.name, version: '2.12.2-unblu-2'
                details.because 'To get the fix of https://github.com/smallrye/smallrye-graphql/pull/2264'
            }
        }
    }

And as far as I can tell the jars are correctly replaced by gradle.

[jmini]

Thank you very much for your help, I think we can close this issue that was more a discussion.