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.

Sign up for GitHub

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

Jump to bottom

Use short names if possible when documenting <see> tags #7

Open
SilentSin opened this issue Apr 25, 2019 · 1 comment
Open

Use short names if possible when documenting <see> tags #7

SilentSin opened this issue Apr 25, 2019 · 1 comment

Comments

@SilentSin
Copy link

image

If I'm already on the page for Animancer.AnimationEventReceiver, it doesn't really need to use the full name when referring to members in that type.

The summary in that image could just be "Constructs a new AnimationEventReceiver and sets the Source and Callback."
@SilentSin
Copy link
Author

Also, the current implementation fails to auto-link to those members.

If I write:

Animancer.AnimationEventReceiver.Source

AnimationEventReceiver.Source

Source

Then only the middle one automatically becomes a link to that member.

@daveaglick daveaglick transferred this issue from statiqdev/Statiq.Web Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SilentSin