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
[api-xml-adjuster] further fix on generic nested type name parsing. (#115)
We have fixed nested [generic type name crashes][1] at 769f944, but
that was only to fix the crash. The resulting type name was not parsed
correctly - namely, the resulting type name dropped the remainings after
the first generic arguments list i.e. in `A<b>.C<d>`, `.C<d>` part had
dropped.
The cause of the problem is somewhat deep, as JavaTypeName and
JavaTypeReference do not consider the possibility that both the nested
generic parent and child have generic arguments.
Anyhow in JavaTypeName now we store the expected information, by
having (hacky) `GenericParent` property to store the expected information.
Now it comes with a test so that it should prove the purpose of the change.
[1]: https://bugzilla.xamarin.com/show_bug.cgi?id=46344
0 commit comments