You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix all instances where generator was using hardcoded type.name instead
of renderName() for TypeScript identifiers. This ensures TypeScript
reserved keywords (like 'class', 'function', 'interface') are properly
escaped with $ prefix when used as GraphQL type names.
Fixed generators:
- MethodsRoot.ts: Interface names and SelectionSets references
- Select.ts: Export type definitions for all GraphQL types
- SelectionSets.ts: Inline fragment property names
- Schema.ts: Type alias definitions
- SchemaDrivenDataMap.ts: Variable names, reference assignments,
operations object, and types array
This extends the fix from #1353 to cover all generator code that
creates TypeScript identifiers from GraphQL type names.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
sddmNodeOutputField.$literal=`// ${Code.termField(propertyNames.nt,outputFieldNamedType.name)} <-- Assigned later to avoid potential circular dependency.`
296
296
// // todo make kitchen sink schema have a pattern where this code path will be traversed.
0 commit comments