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
This would be a great feature because in a number of cases, the exact same documentation from a base class or implemented interface is used by the library code. Even in the same library, there are types that specialise other types, but we would like to keep the same remarks section and maybe change the summary a bit.
The inheritdoc tag should copy all the available documentation for a MemberInfo, and allow overwriting parts of it. For instance, just writing inheritdoc will copy the documentation:
But if I write a summary for the method I expect to have all other documentation copied (parameters, returns, exceptions and so on.) and only have the summary updated.
This feature will extend the documentation lookup because the related XML documentation file needs to be loaded for all referenced assemblies. It is possible that not all referenced assemblies will have their documentation inherited, to reduce the memory print and load time it is okay to implement this extra lookup as a lazy loaded resource from the start.
The text was updated successfully, but these errors were encountered:
This would be a great feature because in a number of cases, the exact same documentation from a base class or implemented interface is used by the library code. Even in the same library, there are types that specialise other types, but we would like to keep the same remarks section and maybe change the summary a bit.
The
inheritdoc
tag should copy all the available documentation for a MemberInfo, and allow overwriting parts of it. For instance, just writinginheritdoc
will copy the documentation:But if I write a
summary
for the method I expect to have all other documentation copied (parameters, returns, exceptions and so on.) and only have thesummary
updated.This feature will extend the documentation lookup because the related XML documentation file needs to be loaded for all referenced assemblies. It is possible that not all referenced assemblies will have their documentation inherited, to reduce the memory print and load time it is okay to implement this extra lookup as a lazy loaded resource from the start.
The text was updated successfully, but these errors were encountered: