Repository navigation
Feature/dashboard UI refactor (#46) - #47
Merged
Merged
Conversation
* refactor(dashboard): declutter the Network detail pane
The Network detail head had grown three stacked strips above the tabs — a
facts row, an actions row, and the tabs themselves — pushing the request and
response panes well down the viewport. Each strip also duplicated something
already on screen: the facts repeated what the compare panes' "General" groups
showed, and the actions row spent a full row on buttons that are used
occasionally, not per-capture.
Consolidate onto the Summary tab and a kebab menu:
- Move the facts strip (time, duration, content type, correlation, mock rule,
vs-original) out of the head and into Summary, where the mock rule keeps its
link into Mocks via a new `mockRuleLink` kv-grid row type.
- Drop the "General" group from both compare panes. Everything it held now
lives in Summary, so the tab is just headers and body.
- Give the failure branch's error string its own `response.error` Summary row
instead of parenthesising it into `response.status`; it was previously only
reachable through the General group that just went away.
- Replace the actions row with a kebab (⋮) menu beside the expand button.
Opt-in per pane via `actionsMenu`, so WebSockets/Push/Crashes — two or three
actions each — keep their flat rows. Items carry the same
`data-detail-action` ids, so the existing delegated handlers are unchanged.
Closes on pick, outside click, and Escape.
- Order Summary first among the tabs. Default selection is still
Request & response.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* docs: specify the Network detail pane layout in DESIGN_SPEC
The spec's Network entry still described a "detail action row (Clone to
composer, cURL, fetch, JSON, Related events)" that predates the current
actions/tabs split, and nothing documented the detail pane's anatomy at all —
so the previous commit's rearrangement had no spec to disagree with.
Add §4a covering the shared head (badge/title/status/expand), the two variants
of its middle band (Network's kebab menu vs. the other panes' flat actions
row), Network's tab order and why Summary leads while Request & response stays
the default selection, the absent "General" group, group collapse defaults,
and Simple-mode hiding.
Also correct three stale claims while in here: §5 named `.list`/`.detail-pane`
(now `.list-pane`/`.detail-pane-v2` inside `.split-shell`), §6's Network
toolbar list omitted the service dropdown and More-filters disclosure, and the
new §4a records that Timeline hand-rolls its own head instead of using
`detailHeadHtml` — logged as an open item rather than left as a silent drift.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix: never let verification block a release build
- Split the packaged scan per format: verify<Variant>DevConsolePackagedArtifact
(APK/AAR, assemble path) and verify<Variant>DevConsolePackagedBundle (AAB,
bundle path). One task naming both built an AAB during every release APK
build, which broke Studio's signing wizard: -Pandroid.injected.apk.location
puts the final AAB inside package<Variant>'s output dir, so Gradle rejects
produce<Variant>BundleIdeListingFile for an undeclared dependency.
- Treat scan-limit-exceeded as a warning, not a violation. R8's mapping file
overran the 64 MiB read cap and failed real release builds.
- Skip BUNDLE-METADATA/ entries: Play strips them, and proguard.map names every
class the build ever saw.
- Warn instead of throwing FileNotFoundException on a missing or unreadable
package.
- Match forbidden paths at any segment, so assets/devconsole-web/ is also found
at base/assets/devconsole-web/ inside an AAB.
- Add devConsole.verificationEnabled / -Pdevconsole.verification.enabled=false
to take verification off assemble/bundle, warning loudly and leaving
verifyDevConsoleProtectedArtifacts runnable by name.
Tests: 11 new functional tests, 42/42 pass. Verified against a real app on both
assembleLiveRelease and bundleLiveRelease with the wizard's injected location.
* docs: align the §4a detail-pane diagram
The box borders didn't line up: the 🔍 and 🔒 emoji are double-width, so the
lines carrying them ran two columns past the frame while every other row sat
short of it. Dropped both emoji and repadded every line to a uniform 62-column
interior, verified by measuring East Asian width rather than counting
characters.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix: support console clipboard fallback and unredacted auth tokens by default
- Add fallback using document.execCommand('copy') when navigator.clipboard or window.isSecureContext is unavailable (e.g. over plain HTTP on LAN)
- Route copyStateJson and copyTableCsv through copyToClipboard with user toast feedback
- Remove authorization headers and Bearer regex pattern from default redaction policy to allow inspecting and copying authorization tokens by default during debugging
- Update documentation in SECURITY_AND_REDACTION.md and THREAT_MODEL.md
- Update unit tests across SDK modules and add regression tests for clipboard copy fallback
Fixes #40
* fix: show the request query string in the network list
Both list surfaces rendered only the captured path, so two calls to the
same endpoint -- /orders?status=open and /orders?status=all -- were two
identical rows and had to be opened one by one to be told apart. The
query was captured and redacted all along; it just never reached the row.
- Add NetworkUrl.queryString (the redacted `a=1&b=2` form display already
built inline) and emit it as "query" beside "path" in the network list
summary JSON, mirrored byte-for-byte in the evidence snapshot
- Web: rowHtml gains an optional mainSub, and Network rows pass the query
into it -- dimmed after the path, with a title carrying both in full,
so the endpoint stays the part that survives the row's ellipsis
- Device: pathWithQuery() reads the query back off the transaction url
and titles the traffic row with it; traffic search matches the query,
and the two url.ifBlank fallbacks no longer drop it
path itself stays bare everywhere: mock-rule prefill escapes it into a
regex, and the path= filter and path facets group on the endpoint alone.
InspectorTransactionUi deliberately gains no field for the same reason --
widening that data class would break its constructor and copy signatures
for every compiled caller, and url already carries the query.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NPxRnPJNgsb3y455VCrDGU
* Fix arraylist visualization issue of showing index of every item in json
* Fix url truncating visualization at both app and web
* Fix "\" issue while copying entire endpoint from app
Add separate create and post request at sample screen
* Fix mock editor keyboard and spacing issues and add full screen response body editing
* Add pretty view with collapsible JSON to the expanded body view at web dashboard
---------
Co-authored-by: Munif <maksudur.munif@pathao.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Co-authored-by: shakibuzzaman <shakib.chowdhury@pathao.com>
Co-authored-by: Md. Asaduzzaman Nur <nur.shuvo@patahao.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nur-shuvo
approved these changes
Sep 29, 2026
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.
The Network detail head had grown three stacked strips above the tabs — a facts row, an actions row, and the tabs themselves — pushing the request and response panes well down the viewport. Each strip also duplicated something already on screen: the facts repeated what the compare panes' "General" groups showed, and the actions row spent a full row on buttons that are used occasionally, not per-capture.
Consolidate onto the Summary tab and a kebab menu:
mockRuleLinkkv-grid row type.response.errorSummary row instead of parenthesising it intoresponse.status; it was previously only reachable through the General group that just went away.actionsMenu, so WebSockets/Push/Crashes — two or three actions each — keep their flat rows. Items carry the samedata-detail-actionids, so the existing delegated handlers are unchanged. Closes on pick, outside click, and Escape.The spec's Network entry still described a "detail action row (Clone to composer, cURL, fetch, JSON, Related events)" that predates the current actions/tabs split, and nothing documented the detail pane's anatomy at all — so the previous commit's rearrangement had no spec to disagree with.
Add §4a covering the shared head (badge/title/status/expand), the two variants of its middle band (Network's kebab menu vs. the other panes' flat actions row), Network's tab order and why Summary leads while Request & response stays the default selection, the absent "General" group, group collapse defaults, and Simple-mode hiding.
Also correct three stale claims while in here: §5 named
.list/.detail-pane(now.list-pane/.detail-pane-v2inside.split-shell), §6's Network toolbar list omitted the service dropdown and More-filters disclosure, and the new §4a records that Timeline hand-rolls its own head instead of usingdetailHeadHtml— logged as an open item rather than left as a silent drift.Tests: 11 new functional tests, 42/42 pass. Verified against a real app on both assembleLiveRelease and bundleLiveRelease with the wizard's injected location.
The box borders didn't line up: the 🔍 and 🔒 emoji are double-width, so the lines carrying them ran two columns past the frame while every other row sat short of it. Dropped both emoji and repadded every line to a uniform 62-column interior, verified by measuring East Asian width rather than counting characters.
Fixes #40
Both list surfaces rendered only the captured path, so two calls to the same endpoint -- /orders?status=open and /orders?status=all -- were two identical rows and had to be opened one by one to be told apart. The query was captured and redacted all along; it just never reached the row.
a=1&b=2form display already built inline) and emit it as "query" beside "path" in the network list summary JSON, mirrored byte-for-byte in the evidence snapshotpath itself stays bare everywhere: mock-rule prefill escapes it into a regex, and the path= filter and path facets group on the endpoint alone. InspectorTransactionUi deliberately gains no field for the same reason -- widening that data class would break its constructor and copy signatures for every compiled caller, and url already carries the query.
Claude-Session: https://claude.ai/code/session_01NPxRnPJNgsb3y455VCrDGU
Fix arraylist visualization issue of showing index of every item in json
Fix url truncating visualization at both app and web
Fix "" issue while copying entire endpoint from app Add separate create and post request at sample screen
Fix mock editor keyboard and spacing issues and add full screen response body editing
Add pretty view with collapsible JSON to the expanded body view at web dashboard
What
One or two sentences on what changed and why (the "why" matters more than the "what" — the diff
already shows the what).
Verification
Which
./gradlewcommands did you run, and what did they confirm? (SeeCONTRIBUTING.md for the standard set.)
./gradlew testDebugUnitTest— passing./gradlew ktlintCheck detekt— clean (or new detekt findings are justified, not baselined away)./gradlew apiCheck— clean, orapiDumpis included in this diff because the public API changedrun for the affected sample(s) (
:samples:<name>:assembleRelease :samples:<name>:verifyDevConsoleProtectedArtifacts)Checklist
RedactionEnginefirst(see docs/README.md for the index)
Anything reviewers should look at closely
Optional — call out anything you're unsure about, a tradeoff you made, or a spot you want a second
look at.