mirror of https://github.com/MHSanaei/3x-ui.git synced 2026-05-13 17:46:02 +00:00

History

MHSanaei 52075a0acd feat(frontend): Phase 5f-iii — inbound add/edit modal + delete/clone/reset Wires up the inbound CRUD flows. The protocol-specific and transport- specific forms are still ahead in 5f-iii-b — for now the modal exposes those as JSON textareas so users can both edit existing inbounds without losing settings and create new ones from default templates. - InboundFormModal.vue: tabbed modal with a full Basics tab (enable, remark, protocol, listen, port, total GB, traffic reset, expiry date) and three JSON-edit tabs (Settings, Stream, Sniffing). Add mode stamps a fresh template per protocol via Inbound.Settings.getSettings(protocol); changing the protocol in add mode restamps the JSON. Edit mode pretty-prints the existing JSON so the user sees the same fields they save back. - POST /panel/api/inbounds/add or /panel/api/inbounds/update/:id on submit; on success the parent refreshes the list and the modal closes. Malformed JSON in any of the three textareas surfaces a message.error and aborts the save without losing user input. - InboundsPage.vue: wires the row action menu to real handlers — edit (opens the modal in edit mode), delete, reset-traffic, clone, reset-clients, del-depleted-clients all go through Modal.confirm and refresh on success. General actions menu wires reset-inbounds / reset-clients / del-depleted-clients the same way. Remaining actions (qrcode/info/import/export/copyClients) still toast as "coming soon" — those land in 5f-iv and 5f-v. - Adds dayjs ^1.11.20 dep for the a-date-picker v-model interop. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-08 13:41:21 +02:00
..
src	feat(frontend): Phase 5f-iii — inbound add/edit modal + delete/clone/reset	2026-05-08 13:41:21 +02:00
.gitignore	build(frontend): Phase 2 — scaffold Vite + Vue 3 + AD-Vue 4	2026-05-08 10:36:03 +02:00
inbounds.html	feat(frontend): Phase 5f-i — inbounds page shell + list fetch	2026-05-08 13:28:15 +02:00
index.html	feat(frontend): Phase 5c-i — index.html dashboard shell	2026-05-08 12:26:51 +02:00
login.html	feat(frontend): Phase 5a — theme system + Vite 8 + vue-i18n 11	2026-05-08 11:11:06 +02:00
package-lock.json	feat(frontend): Phase 5f-iii — inbound add/edit modal + delete/clone/reset	2026-05-08 13:41:21 +02:00
package.json	feat(frontend): Phase 5f-iii — inbound add/edit modal + delete/clone/reset	2026-05-08 13:41:21 +02:00
README.md	build(frontend): Phase 2 — scaffold Vite + Vue 3 + AD-Vue 4	2026-05-08 10:36:03 +02:00
settings.html	feat(frontend): Phase 5d-i — settings page shell + dirty tracking	2026-05-08 13:04:06 +02:00
vite.config.js	feat(frontend): Phase 5f-i — inbounds page shell + list fetch	2026-05-08 13:28:15 +02:00

README.md

3x-ui frontend

Vue 3 + Ant Design Vue 4 + Vite. Builds into ../web/dist/, which the Go binary will embed via embed.FS once the migration reaches the page handlers (Phase 4+).

This directory exists alongside the legacy web/html/ Vue 2 templates during the migration. Pages will move over one at a time on the vue3-migration branch.

Dev

cd frontend
npm install
npm run dev

The dev server runs on http://localhost:5173/ and proxies API calls to the Go panel at http://localhost:2053/ — start the Go panel first (go run main.go), then start Vite.

Production build

npm run build

Outputs to ../web/dist/. The Go binary picks it up at compile time via embed.FS.

Where things live

src/main.js — app entrypoint (createApp, install Antd, mount)
src/App.vue — root component (currently a smoke-test placeholder)
vite.config.js — build + dev-server config
index.html — Vite HTML template

Adding new pages

For each legacy page being migrated, add an entry to vite.config.js rollupOptions.input. Each entry produces its own HTML file in web/dist/, which the Go panel route handler will serve.