DRAFT: feat: Adds getAvoidOptionals to api side GraphQL codegen config when in TypeScript strict mode #9668
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #9633 for the context.
When in strict mode, the desired behavior explain by @cjreimer is to avoid having optionals in the generated types.
This PR is one way we could solve his issue:
Questions remain"
See https://redwoodjs.com/docs/typescript/strict-mode
See https://the-guild.dev/graphql/codegen/plugins/typescript/typescript-operations#avoidoptionals
I think I need some context from @dac09 to determine if this is the correct way to resolve the issue.