fix: use renderName for scalar types to escape TypeScript reserved keywords #1363
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.
Fixes #1354
Summary
bigint
are generated as$bigint
to avoid conflictsProblem
When a GraphQL schema contains a scalar with a name that matches a TypeScript reserved keyword (like
bigint
), the generated code would fail to compile with errors like:Solution
renderName()
function in the scalar generator$