The owners/root page should show repos #117
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub#117
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The owners page ( https://hub.packden.us/ ) should show a list of the owners repos. Make sure the design looks good.
Limit the max number of owners and repos listed. Owners should start from the newest and list in reverse chronological order. Their repos should follow the same.
Additionally, add a (short) paragraph at the top that is well styled about exactly what this application is, and what it does, and how it does it. Make sure it's concise.
Make sure all documentation is up to date around this. This already existed at one point and somehow ended up reverted back to this state.
Fixed by #127 — the owners page now shows each owner's repos (newest-first, capped) plus a short intro card. No new endpoint needed: the core GET /api/v1/owners + /{owner}/repos listing endpoints already existed. Note: the bucket stores no creation timestamps, so newest-first is the reverse of the server's sorted order (documented in 01 §8.1 / 08 / 12 §2.3.1). Git archaeology found no prior per-owner implementation in history (both the vanilla and SolidJS pages listed names only), so this was built fresh.
PR #127 review (branch fix/issue-117, commit
cdc43f3+ review fixup0c7d00b) — verified in scratch worktree, all green.ORDERING QUESTION (issue's explicit demand: newest-first reverse-chron): ACCEPT the reverse-of-server-order proxy, with one wording fix I pushed directly. Verified: Manifest (internal/store/proto/types.go:71-84) has NO CreatedAt (only UpdatedAt/Writer/Revision); GET /api/v1/owners + /{owner}/repos return bare sorted string arrays (internal/api/discovery.go:115-142) fed by ListPrefixes (cmd/walhub/serve.go:508-528); ObjectMeta (internal/store/store.go:28-32) carries no timestamps. So no creation time is reachable on the listing path. CAVEAT the author's phrasing overstated: per-repo creation proxies DO exist deeper in the bucket (CheckpointRef.first_state_at, else first LogEntry.created_at) — they just cost a manifest/log GET per repo, so true reverse-chron needs a server-side shape, not client logic. I tightened the wording in web/src/lib/owners.js:19-29, docs/go/12_web_ui.md:237-241,445, docs/features/01_identity_permissions.md:306-309,383-386, docs/features/08_ui_sdk.md:381 to say 'listing path exposes no creation timestamps'. Follow-up suggestion (new issue): listing endpoints (or a new one) carrying first_state_at per repo so newestFirst() can do true reverse-chron; until then the single-function seam stands.
Other checks, all pass: caps 50/10 enforced client-side (web/src/lib/owners.js:8,14), page bounded to 1+50 SWR GETs; overflow '+N more' links to uncapped /:owner (verified Repos.jsx renders all), owners-overflow terminal text line is correct (no deeper owners view exists); per-owner counts use full-list length (Owners.jsx:35, correct); intro copy accurate — object-store-only/smart-HTTP/disposable-instances, no overclaims (Owners.jsx:78-85); no new deps (no package.json change; imports are solid-js/router/SDK/data only); dark+light via shared .card/.muted + dark: emerald variants, no page-specific colors; keyboard via native router links; Show function-children idiom matches Repos.jsx; 'repos:{owner}' cache key shared between / and /:owner so fetches coalesce. Docs: 01 §8.1 / 08 §6 cache-key rows / 12 §2.3.1 page contract all accurate against 07 §8; AGENTS laws 1/7/8/12 hold (no new endpoint, no new SDK method, docs updated in same line).
Tests: node --test web/test/unit/ → 264/264 pass incl. 7 new owners.test.js (2 transient failures in bare scratch were missing node_modules only — symlinked main worktree's to confirm, unrelated to PR); vite build clean (111 modules, 1.6s). No browser drive (node tests + reasoning per brief; page is links + fetch, no canvas/MIME-sensitive paths).
MERGE RECOMMENDATION: ready to merge.
Fixed by PR #127 incl. review wording fix (ordering proxy honestly documented; true reverse-chron needs a server shape — follow-up suggested), merged. Closing.