fix: Fix input object field introspection with missing defaultValue properties

[llllvvuu]

Summary

If I have no defaultValue, getInputObjectTypeRec will infer my field as foo?: string | null when it should be foo: string. This is because getInputObjectTypeRec only checks for explicity undefined | null. Add a test case and fix for this.

Set of changes

• Additional "description" field in test fixture, which has no defaultValue
• Bugfix and test

[changeset-bot]

🦋 Changeset detected

Latest commit: bf1a7d1

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[kitten]

Nice catch!

I've got a suggestion for the changeset (just a note, this is the exact text that goes in the changelog, so it needs to be user-facing). Same suggestion is already applied to the PR title (fix(x) is generally reserve for sub-packages)

I've got a larger suggestion here for the type change. It seems a bit long and wordy, and as far as I can tell, is a complex multi-part match for a change we can probably do by just adding ? to defaultValue.
Since it's typed as defaultValue?: T | null, and T | undefined | null isn't equivalent, this minimal change should do the trick and seems to pass tests for me locally.

[llllvvuu]

Thanks for the suggestions! I didn't know about ? and it works for me.