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
I am currently working on porting Eto to .NET Core, and the Eto codebase uses a large number of nested types. However, I notice that the VSCode IntelliSense parser does not handle nested types correctly. For example, when I move the mouse over the declaration of Eto.EtoEnvironment.IHandler, the tooltip displays Eto.IHandler. This may cause problems, as by this logic Eto will have dozens of interfaces called IHandler, each of them appearing to be in the same namespace. Note that the C# compiler parses this code properly.
The text was updated successfully, but these errors were encountered:
I am currently working on porting Eto to .NET Core, and the Eto codebase uses a large number of nested types. However, I notice that the VSCode IntelliSense parser does not handle nested types correctly. For example, when I move the mouse over the declaration of
Eto.EtoEnvironment.IHandler
, the tooltip displaysEto.IHandler
. This may cause problems, as by this logic Eto will have dozens of interfaces calledIHandler
, each of them appearing to be in the same namespace. Note that the C# compiler parses this code properly.The text was updated successfully, but these errors were encountered: