graph codegen: handle reserved words

[YaroShkvorets]

Fixes #1896

• Renames fields with reserved name in generated code "yield" -> "yield_"
• Handles all typescript/assemblyscript reserved words
• test

[cloudflare-workers-and-pages]

Deploying graph-tooling with    Cloudflare Pages

Latest commit:	f6ea892
Status:	✅  Deploy successful!
Preview URL:	https://3c35e1f8.graph-tooling.pages.dev
Branch Preview URL:	https://yaro-codegen-reserved-words.graph-tooling.pages.dev

View logs

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphprotocol/graph-cli	0.96.0-alpha-20250128181754-f6ea8924b365aea798fbd645bad0e8a1e539c94a	npm ↗︎ unpkg ↗︎

[changeset-bot]

🦋 Changeset detected

Latest commit: f6ea892

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

This PR includes changesets to release 1 package

Name	Type
@graphprotocol/graph-cli	Minor

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

[0237h]

LGTM but just curious, why isn't safeName also used in the body of the generated code ?

For example here:

graph-tooling/packages/cli/src/codegen/schema.ts

Lines 343 to 352 in f6ea892

	return tsCodegen.method(
	`get ${safeName}`,
	[],
	returnType,
	`
	let value = this.get('${name}')
	${isNullable ? getNullable : getNonNullable}
	`,
	);
	}

[YaroShkvorets]

That would mean renaming these fields in subgraph GraphQL schema, and that's unnecessary and leaks implementation details.