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

Some automatically generated interfaces cannot reference other automatically generated interfaces #73

Open
AustinGrey opened this issue Mar 5, 2025 · 1 comment

Comments

@AustinGrey
Copy link

Thanks for the amazing package. Saves me so much time.

Some interfaces though I cannot use it on, as it causes other automatically generated interfaces to produce invalid code. Here you can see in a service (which has an autogenerated interface) that I'm trying to reference IProjectDeployment , which is also an autogenerated interface.

Image

If I inspect the interface of the service, you can see it didn't give a full path to the IProjectDeployment interface

Image

If I try to manually specify the global::Path.To.NameSpace etc in front of it, that doesn't change anything. If I change the service method to reference the class ProjectDeployment directly, no issues. And if I manually create the interface in the same file as the class, also no issues.

Is it possible because it's used as a generic argument?

Tried on the latest 5.1.3

@ChristianSauer
Copy link
Collaborator

ChristianSauer commented Mar 5, 2025 via email

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

2 participants