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
In the current state the DocumentationMember does not have a property for hence they are not parsed from the file.
This makes sense as there is no direct equivalent in JSDoc. However, when writing custom code generators one might want to include the remarks into the default description etc.
I would suggest to add this to the DocumentationMember class.
[XmlElement(ElementName = "remarks")]
public DocumentationRemarks Remarks { get; set; }
The text was updated successfully, but these errors were encountered:
smkanadl
added a commit
to smkanadl/Reinforced.Typings
that referenced
this issue
Jan 12, 2025
… the <remarks /> section from the XmlDoc. Include tests which also document the need for a <summary /> or <inheritdoc /> section to access it via GetDocumentationMember(). This is mainly to keep backward compatibility with the currently emitted code. reinforced#290
In the current state the
DocumentationMember
does not have a property for hence they are not parsed from the file.This makes sense as there is no direct equivalent in JSDoc. However, when writing custom code generators one might want to include the remarks into the default description etc.
I would suggest to add this to the
DocumentationMember
class.The text was updated successfully, but these errors were encountered: