Long in GraphQL

[uPagge]

When I try to use the Long type, I get a conversion to BigInteger. But it so happened historically that I need to get exactly Long. AdaptToScalar not working

[quarkus-bot[bot]]

/cc @jmartisk, @phillip-kruger

[uPagge]

@jmartisk I have another thought about this. Perhaps I could update the property value at runtime? But a cursory examination of the documentation shows that this is impossible. I found only one way, using

org.microprofile-ext.config-ext:configsource-memory

But the author uses REST to update properties, I would not want to set such an endpoint

Source https://sgitario.github.io/quarkus-update-custom-runtime/

Is there another way to change the property value at runtime?

[phillip-kruger]

I am that author :) you can write your own config source?

[jmartisk]

Changing a property value is one thing, but the problem is that the client instance is built with a particular value and doesn't look into the configuration properties anymore, so it won't see the update.

We could change it so that the client always looks again into the configuration, but it's not as flexible as having an SPI for header provider. And it's also not really good for performance, I think re-reading the configuration is quite expensive.

[uPagge]

Yes, the configuration option is not very successful, and it looks like a crutch, but this is the first thing that came to my mind :)

As a result, so far I have done everything using the Dynamic client.

[jmartisk]

I've reported smallrye/smallrye-graphql#1368 for dynamically supplying headers, let's continue the discussion about it in that issue.

[gsmet]

@phillip-kruger I don’t know where the first screenshot is from but if it’s in our code, I find it weird we translate Longs to BigInteger. Is there a reason for that?

[jmartisk]

But I'm not very happy with the idea of adding a new annotation which does almost the same as @Input, just making it applicable to a parameter... Any better ideas? :/

[phillip-kruger]

Use @input on the parameter ?

[t1]

Hmmm... all parameters are Input, aren't they? All return values are Type.

[jmartisk]

Parameters are inputs, but declaring the input type name via @Input is not possible because that annotation can't be applied to parameters. And it's from the MP spec so we can't simply change it.

• We could add another annotation, but that would make things messy.
• Or we could make it a configuration thing, where we allow the user to pass a configuration map that defines the mapping, like: java.lang.Long (Java class) -> Long (GraphQL type), which is not much nicer.

[phillip-kruger]

It should change on the spec level. If need be we can add a input in smallrye API until it can move to the spec?