Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the id attribute for example nodes #630

Merged
merged 1 commit into from
Sep 9, 2021
Merged

Conversation

baronfel
Copy link
Contributor

@baronfel baronfel commented Sep 8, 2021

Click “Files changed” → “⋯” → “View file” for the rendered RFC.


The `example` XML documentation element is not specified to accept an `id` attribute for purposes of uniquely identifying an
example, but doing so allows tooling to deep-link to a specific example and so should be encouraged. `id` attributes _should_
be url-safe by default, and _should_ be unique across a library.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dsyme question about guidance here: what level of uniqueness scope is enough? Should tools ensure uniqueness via namespacing, or should users ensure uniqueness via naming on their own?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fsdocs isn't exactly great about diagnostics and error failures

I guess it should be "warn if strict is not on, error if it is"

@dsyme dsyme merged commit 725b14b into fsharp:main Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants