Closed ChrisH07 closed 5 years ago
Hm, I fear we are curing the symptoms rather than the root cause of the problem. Normally, the type reference should take part in the name conflict resolution that would automatically fully qualify the type reference in case of a conflict (see NamespaceGenerator.cs in CodeGen). Apparently, this does not work in this case.
But given that you have a concrete problem here, I will merge the changes for a quick fix and try to solve the actual problem in the next couple of days.
Hi Georg. I agree with you that this only solves a symptom and I didn't dig in to this problem deeply at all. If you would like I can provided a sample to reproduce the issue.
Yes, a sample would be greatly appreciated.
Fix for issue #51