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
Currently, the C# language does not provide clear facilities for referencing external content addressable by a URI. This leads to confusion among developers regarding the best plan to include such content in documentation:
This proposal involves three components, each of which should be formalized for inclusion in the language specification.
The href attribute of documentation comment elements is defined, with the value as a URI. The compiler MAY report a warning if the value is not a valid URI.
The see and seealso elements are updated to allow for the use of href attribute. The compiler MAY report a warning if both the cref and href attributes are used for the same reference. The following shows examples of how this may appear:
<seehref="https://github.com/dotnet/csharplang/"/>
<seehref="https://github.com/dotnet/csharplang/">The official repo for the design of the C# programming language</see>
The see and seealso elements are updated to indicate the content of the element, if provided, should be used as the display text of the reference.
This change is likely to not require any core changes in the behavior of the compiler. However, tools (including the IDE component of dotnet/roslyn) are likely to require updates to ensure correct presentation of these references.
The text was updated successfully, but these errors were encountered:
Summary
Motivation
Currently, the C# language does not provide clear facilities for referencing external content addressable by a URI. This leads to confusion among developers regarding the best plan to include such content in documentation:
Detailed design
This proposal involves three components, each of which should be formalized for inclusion in the language specification.
The
href
attribute of documentation comment elements is defined, with the value as a URI. The compiler MAY report a warning if the value is not a valid URI.The
see
andseealso
elements are updated to allow for the use ofhref
attribute. The compiler MAY report a warning if both thecref
andhref
attributes are used for the same reference. The following shows examples of how this may appear:The
see
andseealso
elements are updated to indicate the content of the element, if provided, should be used as the display text of the reference.This change is likely to not require any core changes in the behavior of the compiler. However, tools (including the IDE component of dotnet/roslyn) are likely to require updates to ensure correct presentation of these references.
The text was updated successfully, but these errors were encountered: