Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GlobalScope=true option is not respected in navigation property types #59

Open
buchatsky opened this issue Jan 7, 2022 · 0 comments
Open

Comments

@buchatsky
Copy link

buchatsky commented Jan 7, 2022

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

	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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant