From bd9775af3f5347ae077c01f315e558f416a36457 Mon Sep 17 00:00:00 2001 From: h Date: Wed, 3 Sep 2025 02:16:10 +0300 Subject: [PATCH] docs(agile): properly state nuxt4 in tech-stack.md, define test/unit directory in testing-requirements.md --- docs/architecture/tech-stack.md | 14 +++++++------- docs/architecture/testing-requirements.md | 2 +- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/architecture/tech-stack.md b/docs/architecture/tech-stack.md index 846cfd4..7d6b990 100644 --- a/docs/architecture/tech-stack.md +++ b/docs/architecture/tech-stack.md @@ -1,9 +1,9 @@ # 3. Tech Stack (Revised) -| Category | Technology | Version | Purpose & Rationale | -| :--- | :--- | :--- | :--- | -| **Fullstack Framework**| **Nuxt** | `^4.0.3` | Core framework for both frontend and backend (server routes). | -| **Database ORM** | **Prisma** | `latest` | Next-generation ORM for type-safe database access and automated migrations. | -| **Database** | **PostgreSQL** | `latest` | Robust, reliable SQL database managed by Prisma. | -| **Deployment** | **Docker Compose**| `latest` | For containerizing and managing the application stack. | -| ... | *(rest of the stack remains the same)* | ... | ... | +| Category | Technology | Version | Purpose & Rationale | +| :--- | :--- | :--- |:---------------------------------------------------------------------------------------------------------------| +| **Fullstack Framework**| **Nuxt** | `^4.0.3` | Core framework for both frontend and backend (server routes). Note that its structure differs from Nuxt 3 and you should check context7 for details | +| **Database ORM** | **Prisma** | `latest` | Next-generation ORM for type-safe database access and automated migrations. | +| **Database** | **PostgreSQL** | `latest` | Robust, reliable SQL database managed by Prisma. | +| **Deployment** | **Docker Compose**| `latest` | For containerizing and managing the application stack. | +| ... | *(rest of the stack remains the same)* | ... | ... | diff --git a/docs/architecture/testing-requirements.md b/docs/architecture/testing-requirements.md index aa564ea..f3162f0 100644 --- a/docs/architecture/testing-requirements.md +++ b/docs/architecture/testing-requirements.md @@ -3,5 +3,5 @@ Testing is critical for ensuring the integrity of the system. * **Unit Tests:** We will use **Vitest** for unit testing. Every composable and service function must have unit tests covering its logic. * **Component Tests:** We will use **`@vue/test-utils`** to test individual Vue components. Tests should verify that components render correctly based on props and that they emit events when interacted with. -* **Test Location:** All test files will be located alongside the file they are testing, with a `.spec.ts` extension (e.g., `useLedger.spec.ts`). +* **Test Location:** All test files will be located alongside the file they are testing, with a `.spec.ts` extension (e.g., `useLedger.spec.ts`). Server tests will be located in the `test/unit` directory.