feat(chatelet): guest booking UI — slice 1 (browse + availability) #142
No reviewers
Labels
No labels
app:activities
app:chat
app:events
app:forum
app:libra
app:market
app:restaurant
app:tasks
app:wallet
app:webapp
bug
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aiolabs/webapp!142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/chatelet-guest-ui"
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?
Slice 1 of the chatelet guest booking UI (#141): the standalone app + read-only browse rooms → room detail → date-range availability check. Booking→pay→confirm is slice 2.
What's here
Standalone app (mirrors
events):chatelet.html,src/chatelet-app/{main,app,App,app.config,views/SettingsPage},vite.chatelet.config.ts(port 5188,dist-chatelet, manifest idaiolabs-chatelet), +dev:/build:/preview:chateletscripts and entries indev:all/build:demo(VITE_BASE_PATH=/chatelet/).Module
src/modules/chatelet/:ChateletApiService— plain HTTP wrapper (theTicketApiServicepattern) hitting chatelet's public guest endpoints (GET /public/rooms[/{id}],POST /availability). Unauthenticated by default.useChateletcomposable + pinia store, services via DI (tryInjectService, never direct import).ChateletPage(room grid) +ChateletDetailPage(details + date pickers → availability with sats/fiat quote; Book stubbed for slice 2).SERVICE_TOKENS.CHATELET_API.Transport note
HTTP-for-now: chatelet's kind-21000 RPC surface exists but the webapp's RPC client is disabled post-#9 (aiolabs/lnbits#64). When that lands, only
ChateletApiServiceswaps HTTP→RPC — no view changes. Backend endpoints shipped in chatelet v0.3.0 (in the catalog; upgrade chatelet on aio-demo to serve them).Verified
npm run build:chatelet—vue-tsc -btypechecks clean + Vite bundles the whole app (views chunked, PWA generated, built in 3.5s).npm run dev:chatelet(port 5188) against an aio-demo with chatelet ≥ v0.3.0, or wait for the staging deploy. PointVITE_LNBITS_BASE_URLat the instance.Follow-ups
app:chateletlabel (couldn't create via MCP); appliedenhancement.Release flow
Per webapp rules this targets
dev(staging). Handing off merge to you via the Forgejo UI.🤖 Generated with Claude Code
chatelet.html + src/chatelet-app/{main,app,App,app.config,views/SettingsPage} + vite.chatelet.config.ts (port 5188, cacheDir .vite-chatelet, dist-chatelet, manifest id aiolabs-chatelet), mirroring the events standalone. package.json gains dev:/build:/preview:chatelet + entries in dev:all and build:demo (VITE_BASE_PATH=/chatelet/). Verified: build:chatelet typechecks + bundles clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019VUQCfdqiLSsFS2jcGnaFDView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.