[10.0] API doc cross-links #36336
Merged
[10.0] API doc cross-links #36336
Conversation
This file contains hidden or 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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates documentation across multiple ASP.NET Core files by adding API documentation cross-references (xref links) to replace inline code references and text descriptions. The changes primarily target .NET 10.0 content, converting method names, property names, and type references to proper xref syntax that links to official API documentation.
Key Changes
- Replaced inline code-styled API references with xref syntax throughout passkeys, Blazor, and OpenAPI documentation
- Removed "UPDATE 10.0" comment markers indicating that API cross-links have been completed
- Updated metadata dates to reflect documentation changes
- Cleaned up preview-specific content and comments for the .NET 10.0 release
Reviewed Changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| aspnetcore/security/authentication/passkeys/index.md | Added xref links for Identity passkey APIs including IdentityPasskeyOptions properties, SignInManager methods, and UserPasskeyInfo; updated ms.date metadata |
| aspnetcore/security/authentication/passkeys/blazor.md | Cleaned up preview SDK references and simplified prerequisites section |
| aspnetcore/fundamentals/openapi/customize-openapi.md | Added xref for AddOpenApiOperationTransformer API |
| aspnetcore/blazor/state-management/server.md | Added xref links for CircuitOptions properties and PersistentState attribute; contains grammar error |
| aspnetcore/blazor/state-management/prerendered-state-persistence.md | Added consistent xref links for PersistentState attribute usage across multiple sections |
| aspnetcore/blazor/javascript-interoperability/index.md | Added xref links for JS interop methods including InvokeConstructorAsync, GetValueAsync, and SetValueAsync |
| aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md | Added comprehensive xref links for JSRuntime methods and IJSObjectReference APIs |
| aspnetcore/blazor/forms/validation.md | Added xref links for ValidationServiceCollectionExtensions.AddValidation and ValidatableType attribute |
| aspnetcore/blazor/forms/input-components.md | Added xref link for InputHidden component |
| aspnetcore/blazor/components/quickgrid.md | Added xref links for QuickGrid component methods (RowClass, HideColumnOptionsAsync) and fixed moniker range placement |
| aspnetcore/blazor/components/integration.md | Added xref link for PersistentState attribute |
| aspnetcore/blazor/call-web-api.md | Added xref links for JsonPatch APIs; contains incorrect NuGet package URL |
Co-authored-by: Copilot <[email protected]>
wadepickett
approved these changes
Nov 12, 2025
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.
Fixes #36335
Only one review needed.
Anywhere that you see "MIA API," I'll need to talk to the PU about the API missing. We'll need to file requests to get it marked for inclusion. I'll take care of it later. 🏃♂️
Internal previews
Toggle expand/collapse