Reverse engineer C# generics

[PaulH]

The reverse engineering of generics is still slightly broken; sometimes it gets it correct other times wrong.

One issue I've found is when you have two classes with the same name only difference by the generic types, e.g. IDao and IDao<T, ID>.

It gets confused and diagrams that IDao<T, ID> inherits from itself rather than IDao.

Should I just report stuff like this as a bug?

[«Midnight»]

The reverse engineering of generics is still slightly broken; sometimes it gets it correct other times wrong.

One issue I've found is when you have two classes with the same name only difference by the generic types, e.g. IDao and IDao<T, ID>.

It gets confused and diagrams that IDao<T, ID> inherits from itself rather than IDao.

Should I just report stuff like this as a bug?

Yes you should Paul,

But please do not "just" report it. Search my recent posts for a best practice we've been using to keep both Sparx and the user community in the loop on these.

To make your search easier, we use the same practice for bugs and feature requests. You'll find the latter easier to search for.

David