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
When GlobalScope option is set to True, the type definitions are generated correctly in the global scope (without a surrounding module). But if one entity references another the reference type is generated incorrectly with DefaultModuleName prefix despite GlobalScope=True:
Current behavior
class Supplier {
...
}
class Product {
productId: number;
...
supplierId?: number;
supplier: server.Supplier;
}
If DefaultModuleName is an empty string, it is generated as supplier: .Supplier;
Expected behavior
class Product {
...
supplier: Supplier;
}
Installed product versions
Visual Studio: 2022 Community
This extension: 1.3.53
The text was updated successfully, but these errors were encountered:
Description
When GlobalScope option is set to True, the type definitions are generated correctly in the global scope (without a surrounding module). But if one entity references another the reference type is generated incorrectly with DefaultModuleName prefix despite GlobalScope=True:
Current behavior
If DefaultModuleName is an empty string, it is generated as
supplier: .Supplier;
Expected behavior
Installed product versions
The text was updated successfully, but these errors were encountered: