Phillip Krüger

That is why this is still a draft. Busy with the 2.0.0.RC release

@gsmet Yes native failed due to new i18n resource from graphql-java. Fixed now. Should be ok, lets see what CI does now.

Thanks @gsmet !

I have not looked at this yet. If you create a small reproducer that makes it easier

I already discussed with @geoand on Friday he gave me a few idea to go and look for. I'll continue tomorrow on this.

@geoand I'll check, why would that be an issue ?

I pinged @stuartwdouglas , he is helping out. I am hopeful we will get this fixed soon.

2.11.2 might have fixed your case, the PRs that followed fix similar cases but for the Graphql context

+1 for this enhancement :)

Thanks @dicolasi . This case is when you have an Integer (Object) rather than a primitive, and it can be null. So it would be good to allow `@Nullable` on...