chore: planning docs + backend/frontend scaffold + MVP Prisma schema
- CLAUDE.md, ARCHITECTURE.md, TASKS.md per Lastenheft-Vorgabe - ApiCore-Backend: NestJS scaffold, Prisma 7 (DATABASE_URL via prisma.config.ts) - ApiCore-Frontend: Next.js App Router scaffold (TS, Tailwind, ESLint) - prisma/schema.prisma: alle MVP-Entitaeten aus Abschnitt 13/4.2-4.22/26, validiert und Client generiert Grundgeruest (TASKS.md #0) noch nicht vollstaendig: shadcn/ui, TanStack Query, PWA-Manifest, deploy/k8s/, Dockerfiles fehlen noch.
This commit is contained in:
commit
c4a2d0648e
255 files changed
+46918
No files matched your search
@@ -0,0 +1,18 @@
|
||||
import { defineConfig, globalIgnores } from "eslint/config";
|
||||
import nextVitals from "eslint-config-next/core-web-vitals";
|
||||
import nextTs from "eslint-config-next/typescript";
|
||||
|
||||
const eslintConfig = defineConfig([
|
||||
...nextVitals,
|
||||
...nextTs,
|
||||
// Override default ignores of eslint-config-next.
|
||||
globalIgnores([
|
||||
// Default ignores of eslint-config-next:
|
||||
".next/**",
|
||||
"out/**",
|
||||
"build/**",
|
||||
"next-env.d.ts",
|
||||
]),
|
||||
]);
|
||||
|
||||
export default eslintConfig;
|
||||
Reference in new issue
Block a user