fix: handle explorer directory path segments - #27
Merged
Conversation
thiennamdinh
force-pushed
the
fix-explorer-directory-pairs
branch
from
June 17, 2026 17:35
16076d1 to
bd365b8
Compare
Summary - Parse ledger directory pair entries without stringifying the entry type into child path segments. - Add Explorer-side R7RS/percent path segment encoding for create, upload, and rename operations. - Decode escaped path segments for display while preserving encoded segments for API calls. - Bump the release metadata and compose image defaults to 1.3.2. - Update release CI so versioned main merges promote branch-validated SHA images instead of rebuilding expensive main-branch multi-arch images. - Refresh WebDAV/path/release docs for API-token auth, service-side escaping, Windows client limitations, and cargo-chef cache expectations. Testing - cd services/explorer && npm test -- --watchAll=false - cd services/explorer && npm run build - Live Playwright checks against djali.net verified existing file content renders, files with spaces can be created and selected, and decoded names are displayed while encoded symbols are used at the ledger boundary. Notes/Risks - The hosted Explorer was temporarily rebuilt locally under the 1.3.1 tag; this release moves official artifacts to 1.3.2 rather than reusing 1.3.1. - Windows built-in WebClient/MiniRedir remains best-effort; dedicated clients such as rclone with WinFsp are documented as the fallback.
thiennamdinh
force-pushed
the
fix-explorer-directory-pairs
branch
from
June 17, 2026 17:59
190a3a6 to
8076de7
Compare
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.
Summary
[name, type]without stringifying the whole pair as a child name.1.3.2for an immutable patch release tag.Testing
cd services/explorer && npm test -- --watchAll=falsecd services/explorer && npm run build['*state*', 'tdinh', 'hello-2.txt']returns a byte-vector while the previous bad pathhello-2.txt,valuereturnsnothing.djali.netconfirmed:nothing;path-error;djali.netafter redeploy.1.3.2main merge can promote SHA-tagged artifacts.Notes/Risks
djali.netExplorer has been temporarily rebuilt locally with this fix under the1.3.1image tag; this PR bumps the official release target to1.3.2rather than reusing the published1.3.1tag.