[docs] Document ResourceUrlAnnotation.DisplayOrder - #1806
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Documents changes from microsoft/aspire#20637 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
6 of 14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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
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.
Documents changes from microsoft/aspire#20637
@eerhardtTarget branch
Targeting
release/17.0based on the source PR milestone17.0.Why this is needed
microsoft/aspire#20637 makes
ResourceUrlAnnotation.DisplayOrdera non-obsolete, nullable read/writeintproperty (previously an obsolete field), allowing consumers to control the sort order of custom resource URLs in the dashboard without obsolete warnings. Higher values sort higher in the dashboard. This is a user-facing API change with a documented "User-facing usage" example in the source PR, and no existing page on aspire.dev mentionedDisplayOrder, so a docs update was needed.What changed
fundamentals/custom-resource-urls.mdx, right after the existing "Customize endpoint URL" section, explaining theDisplayOrderproperty and showing aWithUrlForEndpointexample settingurl.DisplayOrder = 1000;(mirroring the source PR's example).Files modified
src/frontend/src/content/docs/fundamentals/custom-resource-urls.mdx(updated — existing page, no new pages created)