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
Audit note, issue left open. This looks done: the TypeScript generator resolves cross-schema names through the symbol table (generation codegen/src/symbols.rs, whose header records that comline-typescript#32 fixed it) and writes an import header with 'declared as bound' aliasing (golden import_alias/typescript/api.ts: import type { Shared as Aliased }), and comline-typescript#119 and #169 followed. What is missing is proof for the exact case in the title: no fixture has two schemas declaring the same name. A fixture like that would settle it and let this be closed.
Activity
Kinflou commentedon Nov 15, 2026
Audit note, issue left open. This looks done: the TypeScript generator resolves cross-schema names through the symbol table (generation codegen/src/symbols.rs, whose header records that comline-typescript#32 fixed it) and writes an import header with 'declared as bound' aliasing (golden import_alias/typescript/api.ts: import type { Shared as Aliased }), and comline-typescript#119 and #169 followed. What is missing is proof for the exact case in the title: no fixture has two schemas declaring the same name. A fixture like that would settle it and let this be closed.
Kinflou commentedon Nov 15, 2026
A fixture that settles this is filed as ComlineProject/generation#156: two schemas declaring the same type name, with goldens for both generators.