find_err_detail relied on ReturnDict.serializer, so plain string and list errors lost their message and nested ones could raise. Walk dicts and lists directly instead, and keep the internal non_field_errors key out of user-facing text. The axios interceptor toasted every failure before the page could handle it, so saving over the mindmap limit showed two messages and the workbench fell back to a generic one. Add an opt-in silentError flag and let the workbench render the server message itself. |
||
|---|---|---|
| .. | ||
| env | ||
| public | ||
| src | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .prettierrc.json | ||
| README.md | ||
| admin.html | ||
| chat.html | ||
| env.d.ts | ||
| eslint.config.ts | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
README.md
ui
This template should help get you started developing with Vue 3 in Vite.
Recommended IDE Setup
VSCode + Volar (and disable Vetur).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need Volar to make the TypeScript language service aware of .vue types.
Customize configuration
See Vite Configuration Reference.
Project Setup
npm install
Compile and Hot-Reload for Development
npm run dev
Type-Check, Compile and Minify for Production
npm run build
Lint with ESLint
npm run lint
测试提交