Repository navigation
refactor: remove map view and default dashboard to pages - #227
Merged
Merged
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
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.
Why
The map does not help the owner resume useful work, and maintaining the current explorer adds substantial complexity. Remove it now and leave the design of a recent-context visualization for a separate change.
How
Remove the map across the frontend and backend, including its API, graph service and queries, rendering, navigation, cache invalidations, and wheel-picker dependency. Pages becomes the default owner dashboard and demo destination. Shared resource previews, mentions, references, and temporal coverage remain available. Retain the page-mention covering index because it also speeds current page-detail and publication dependency reads.