[docs] Fix links to defaults #664
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@hakenr currently,
HxGrid.Defaultsleads to a non-existent page, this commit adjusts the URL, so that it leads to theGridSettingstype definition.However, to be consistent with other links to properties, we should change the link to lead to the page of the type where the property is defined, in this example
HxGrid.And since we gained the support for hashed routing to named elements in .NET 8, I suggest we consider setting the Ids of members (properties, methods, ...) in the API documentation section to increase the usefulness of the links to component members.