[typescript-resolvers] Refactor to remove NameNode override and simplify federation functions #10377
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.
Description
To prepare for next major version, we want to fix a few long-standing type cast issues for
typescript-resolvers
plugin and federation support:NameNode
was implemented to change how a node name can be accessed. Instead ofnode.name.value
, it just becomesnode.name
. However, the type of this node (fromgraphql
package) does not know that this is changed at runtime, so we always need to type caseas any as string
oras unknown as string
to satisfy TypeScript. This results in confusion for contributors, and normally requires runtime debug to understand/correctly use the right value.NameNode
function to avoid typecasts laterfederation.ts
take both AST nodes and types. This adds more complexity as there are more code paths to think about.Type of change
How Has This Been Tested?