I have some problems with nullability (not "undefi...

# graphql-kotlin

[Tobias]

I have some problems with nullability (not "undefinability"). I don't believe it's kotlin-graphql's fault, I just want to confirm the behaviour. If I understand this correct as per
https://opensource.expediagroup.com/graphql-kotlin/docs/schema-generator/execution/optional-undefined-arguments/
I should not get NPE when doing
fun optionalInput(value: String? = null): String? = value
where value is null in the graphql variables, right? I should just get the value of null?

[Dariusz Kuc]

yes if you don't specify value it should use the provided default value of null

[Dariusz Kuc]

if you are getting NPE -> are you setting the defaults?

[Tobias]

yes, but like I said, I don't believe it's kotlin-graphql's fault

[Tobias]

I get it in the Armeria graphql wrapper that seems to assume all values sent are non-null. I just wanted to confirm I didn't misunderstand something

[Tobias]

Either way, thanks for the confirmation

[Tobias]

Although the question is what happens when I send in null

[Tobias]

"`undefined`" works, it's the null that makes things go boom

[Dariusz Kuc]

maybe it doesn't make a distinction between defined, null and undefined?

[Dariusz Kuc]

e.g. Kotlin/Java by itself does not

[Dariusz Kuc]

JS does

[Tobias]

Just confirmed it's a bug in Armeria

[Tobias]

I'll write a bug report for them. Thanks for your help!

[Tobias]

Yes, the client is Apollo JS

[Tobias]

Armeria make a map with all the values in parameters object. Sending undefined in Apollo is fine, because then it literally does not exist in the sent data. Null is not, because for some reason the map implementation used by Armeria does not allow null values.

[Dariusz Kuc]

👍