Repository navigation
[docs] Document browser-stored dashboard tags, order and metric pins - #2074
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
aspire-repo-bot
Bot
added
the
docs-from-code
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#21840
Author:
@davidfowl-unknownTargeting
release/17.0, the latest release branch onmicrosoft/aspire.dev. The source PR milestone17.1has no matching branch there (latest_release_fallback).Why: The source PR moves resource tags, resource and group order, and pinned metrics from the SQLite settings database to browser local storage. The dashboard docs didn't describe where these settings live.
Changes (updated page):
src/frontend/src/content/docs/dashboard/data-persistence.mdx: added a "Browser-stored settings" section covering the storage keys, per-browser and per-origin scope, unprotected storage, multi-tab merging, and the_Unreadablebackup.Triggered signals:
dashboard_user_facing_page_changedandnew_public_type.