@pasosdejesus/m 0.22.0 → 0.22.1

package/src/test-utils/README.md

@@ -4,17 +4,17 @@
 
 This directory contains generic mocking utilities for tests, designed to be reusable across multiple projects using similar stacks. These utilities have been extracted and adapted from the `learn.tg` project to become part of the `@pasosdeJesus/m` library.
 
-### 🕊️ Christian Framework
+### Christian Framework
 
 As part of "Pasos de Jesús" projects, we recognize that our work serves a higher purpose: to bring the Good News to the world through technology. The Word of God is our supreme compass (brújula suprema). We strive to act with faithful diligence, excellence, and love, remembering that our technical work ultimately serves God's kingdom.
 
 "Whatever you do, work at it with all your heart, as working for the Lord, not for human masters" (Colossians 3:23). This includes writing tests and creating tools that help others build reliable, truthful software.
 
-## 🚀 For users of projects generated by `m`
+## For users of projects generated by `m`
 
 If you're developing a project generated with `m`, you can use these test utilities by importing them directly from the `@pasosdejesus/m` package.
 
-> ⚠️ **Vitest compatibility**: These mocks are designed for **Vitest 2.1.x**.
+> [WARN] **Vitest compatibility**: These mocks are designed for **Vitest 2.1.x**.
 > They use `vi.hoisted()` and `vi.mock()`. For vitest 1.x, use version `0.14.x`
 > of `@pasosdejesus/m`.
 
@@ -61,7 +61,7 @@ Esto configura automáticamente:
 - **axios**: delegación a `mocks.mockAxiosGet/Post/Put/Delete/Request`
 - **siwe**: `SiweMessage`
 
-> ⚠️ **CRÍTICO**: `vi.mock()` debe estar a **module scope** del archivo que vitest transforma.
+> [WARN] **CRÍTICO**: `vi.mock()` debe estar a **module scope** del archivo que vitest transforma.
 > No funciona desde funciones dentro de módulos importados (como `setupMocks()`).
 > Si usas `apiDbMocks.setupMocks()`, el `vi.mock('kysely')` interno **no se aplica**.
 > Agrega los `vi.mock()` directamente en tu `vitest.setup.ts` o en el test file.
@@ -122,7 +122,7 @@ describe('My test', () => {
 
 Check the example file included in your project: `templates/tests/test-utils.example.test.ts`.
 
-## 📁 Structure
+## Structure
 
 ```
 test-utils/
@@ -139,7 +139,7 @@ test-utils/
 > (credenciales, deployments, ecosystem-addresses, slearn-info) están en
 > `@pasosdejesus/mpdj/test-utils`. Ver [`packages/mpdj/src/test-utils/README.md`](../../mpdj/src/test-utils/README.md).
 
-## 🧪 Available Modules
+## Available Modules
 
 ### 1. `fs-mocks.ts` – Filesystem
 
@@ -181,7 +181,7 @@ beforeEach(() => {
 - `createMockDb()`: Flat mock DB object with chainable methods — simple, no class needed
 - `apiDbMocks` / `libDbMocks`: Pre-configured instances for API routes and libraries
 
-> ⚠️ **CRÍTICO**: `vi.mock()` debe estar a **module scope**. El método `setupMocks()`
+> [WARN] **CRÍTICO**: `vi.mock()` debe estar a **module scope**. El método `setupMocks()`
 > llama `vi.mock()` internamente pero vitest **no lo hoistea** porque está dentro de
 > una factory en un módulo importado. Agrega los `vi.mock()` directamente:
 
@@ -377,7 +377,7 @@ viemMocks.createPublicClient.mockReturnValue({ ... })
 - Mock chains are extensible; add new chains as needed
 - **Lesson learned:** Some functions like `privateKeyToAccount` and `formatUnits` are necessary for transaction tests
 
-## 🚀 Complete Usage Examples
+## Complete Usage Examples
 
 ### Configuration for API Route Tests
 
@@ -432,7 +432,7 @@ test('renders component with wallet connection', () => {
 })
 ```
 
-## 📝 Important Lessons Learned
+## Important Lessons Learned
 
 ### 1. **Import order**
 Radix UI mocks must be imported **before** importing any components that use them. Place `import '@pasosdejesus/m/test-utils/radix-mocks'` at the beginning of test files.
@@ -460,11 +460,11 @@ Configure mocks to simulate errors (e.g., `mockRejectedValue`) to test error flo
 ### 8. **`vi.mock` hoisting in Vitest (CRÍTICO)**
 `vi.mock` calls are hoisted to the top of the **file being transformed by vitest**. NO se hoistean desde funciones dentro de módulos importados. Ejemplo:
 ```typescript
-// ❌ NO FUNCIONA — el vi.mock está dentro de setupMocks() en un módulo importado
+// [FAIL] NO FUNCIONA — el vi.mock está dentro de setupMocks() en un módulo importado
 import { apiDbMocks } from '@pasosdejesus/m/test-utils'
 apiDbMocks.setupMocks() // vi.mock('kysely') interno NO se aplica
 
-// ✅ FUNCIONA — vi.mock() a module scope del archivo que vitest transforma
+// [OK] FUNCIONA — vi.mock() a module scope del archivo que vitest transforma
 vi.mock('kysely', () => ({ Kysely: MockKysely, PostgresDialect: vi.fn(), sql: mockSql }))
 ```
 Esto aplica a TODOS los `setupMocks()` de los test-utils. Para usar `apiDbMocks` correctamente, agrega el `vi.mock()` a module scope en tu `vitest.setup.ts` (ver ejemplo en §2).
@@ -534,14 +534,14 @@ Ensure that React versions are consistent between the test utilities package and
 ### 15. **Global React setup for mocks**
 When using Radix UI mocks or other React-based mocks in Vitest setup files, set `global.React = React` before importing the mocks to ensure proper React instance sharing. This is especially important when mocks are used in `vitest.setup.ts`.
 
-## 🔧 Configuration for Other Projects
+## Configuration for Other Projects
 
 These utilities can be used in other projects with the following adaptations:
 
 ### 1. **Kysely Configuration**
 If the project uses a different path for Kysely configuration:
 ```typescript
-// ⚠️ configPath currently non-functional due to vi.mock hoisting
+// [WARN] configPath currently non-functional due to vi.mock hoisting
 // For different paths, configure aliases in Vite or mock manually
 createMockKysely({ skipConfigMock: true }) // And mock the module manually
 ```
@@ -594,7 +594,7 @@ export function getMyMocks() {
 }
 ```
 
-## 🤝 Contribution
+## Contribution
 
 The utilities are designed to be part of `@pasosdeJesus/m`. To contribute:
 
@@ -603,7 +603,7 @@ The utilities are designed to be part of `@pasosdeJesus/m`. To contribute:
 3. **Test**: Ensure utilities work across multiple projects
 4. **Christian principles**: Work with diligence, humility, and love (Colossians 3:23)
 
-## 🚀 Integration with Existing Projects
+## Integration with Existing Projects
 
 These utilities are now part of the `@pasosdeJesus/m` package and ready to use. They have been successfully integrated into the `learn.tg` project, serving as a reference implementation.
 
@@ -643,7 +643,7 @@ beforeAll(() => {
 });
 ```
 
-## 📄 License
+## License
 
 Part of `@pasosdeJesus/m` – Utilities for "Pasos de Jesús" projects.