René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"QAPage","mainEntity":{"@type":"Question","name":"Is the data loader's per-key context allowed to be null?","text":"
Based on looking at the code and testing it, it appears that this data fetcher will pass through the key context to the data loader, even if it's null:
\n
    TypeRuntimeWiring.newTypeWiring(\"Query\")\n        .dataFetcher(\n            \"myField\",\n            environment -> {\n              String myId = environment.getArgument(\"myId\");\n              \n              // it's OK if this is null, because the keyContext is allowed to be null?\n              Integer myKeyContext = getNullableKeyContext(...);\n\n              return environment.getDataLoader(\"myLoader\").load(myId, myKeyContext);\n            })\n        .build();\n
\n
Can you confirm, that though? Because nothing I found in the Javadocs or https://www.graphql-java.com/documentation/v16/batching#passing-context-to-your-data-loader says whether the per-key context is allowed to be null.
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"
Yes they can be null
","upvoteCount":2,"url":"https://github.com/graphql-java/java-dataloader/discussions/94#discussioncomment-1094039"}}}