Remove redundant Metadata button from end-user views#955
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…geView, ReportView Removed the visible </> Metadata button from end-user view headers. The MetadataInspector panel now only opens via ?__debug URL parameter. ObjectView retains its admin Design Tools menu entry for metadata inspection. Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove redundant Metadata button for improved user experience
Remove redundant Metadata button from end-user views
Mar 2, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the end-user-facing </> Metadata header toggle from several Console views to avoid duplicating the existing debug entry points (?__debug and Ctrl+Shift+D), while keeping the metadata inspector panel available for developer/debug workflows.
Changes:
- Removed
<MetadataToggle>from the headers of RecordDetailView, DashboardView, PageView, and ReportView. - Kept
<MetadataPanel>wired toshowDebugso it still opens when debug mode is active (e.g., via?__debug). - Cleaned up related imports/usages (
MetadataToggle,toggleDebug) in the affected views and documented the change inROADMAP.md.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| apps/console/src/components/ReportView.tsx | Removes header metadata toggle; retains metadata panel controlled by showDebug. |
| apps/console/src/components/RecordDetailView.tsx | Removes header metadata toggle; retains metadata panel controlled by showDebug. |
| apps/console/src/components/PageView.tsx | Removes header metadata toggle; keeps debug-driven metadata panel and existing edit button behavior. |
| apps/console/src/components/DashboardView.tsx | Removes header metadata toggle; retains metadata panel controlled by showDebug. |
| ROADMAP.md | Adds a completed roadmap entry documenting the unified debug/metadata entry change. |
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.
RecordDetailView, DashboardView, PageView, and ReportView all expose a
</> Metadatatoggle button in the header that serves no purpose for end users and duplicates the existing?__debug/Ctrl+Shift+Ddebug panel. ObjectView already gates this behind an admin-only Design Tools menu.Changes
<MetadataToggle>button from RecordDetailView, DashboardView, PageView, ReportView headers<MetadataPanel>— still auto-opens when?__debugURL param is present, preserving developer accessMetadataToggleandtoggleDebugreferences from all four viewsThe
MetadataTogglecomponent anduseMetadataInspector().toggleDebugremain exported for ObjectView's Design Tools menu, which is unchanged.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.