Skip to content

Conversation

@kennykerr
Copy link
Collaborator

Fixes #892

Adds a simple test class to ensure this works.

@kennykerr kennykerr merged commit 1935608 into master Mar 26, 2021
@kennykerr kennykerr deleted the windows-namespace branch March 26, 2021 18:56
@DefaultRyan
Copy link
Member

The test case covers the type name appearing in isolation, but I was expecting to also see issues with parameter and field types. Your test class also needs to have methods/properties that use things from a Windows namespace. Windows.Foundation.Uri comes to mind.

At least that's the approach I was planning as I started looking at this.

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

Successfully merging this pull request may close these issues.

Code generation fails when creating a component with a nested Windows namespaces

3 participants