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
The IApplicationBuilder in the summary text is colored as a class. This is because the information is read as an XML doc, and the type is given the "type" tag. This tag has no information about if the type it is referring to is a class, interface, or struct. Currently, VS tooling (VS layer, not FCS layer) reads this and defaults to class since it's probably assumed to be the most common.
A quick hack would be to see if the name starts with I, then treat it as an interface. But that's a hack.
To do this properly, we would need to read this data and build a mapping between the fully-qualified type and a real symbol we resolve. This would then tell us which kind of type it is, and we could tag it appropriately.
Labeling this as a bug because it seems like a bug from the user's perspective, but it is actually a fundamental change we have to make.
The text was updated successfully, but these errors were encountered:
dsyme
changed the title
Cannot reasonably represent interfaces or structs from XML documentation
Highitling can't represent interfaces or structs from XML documentation
Sep 1, 2020
Consider the following tooltip:
The
IApplicationBuilder
in the summary text is colored as a class. This is because the information is read as an XML doc, and the type is given the "type" tag. This tag has no information about if the type it is referring to is a class, interface, or struct. Currently, VS tooling (VS layer, not FCS layer) reads this and defaults to class since it's probably assumed to be the most common.A quick hack would be to see if the name starts with
I
, then treat it as an interface. But that's a hack.To do this properly, we would need to read this data and build a mapping between the fully-qualified type and a real symbol we resolve. This would then tell us which kind of type it is, and we could tag it appropriately.
Labeling this as a bug because it seems like a bug from the user's perspective, but it is actually a fundamental change we have to make.
The text was updated successfully, but these errors were encountered: