Ci GitHub actions

[ekumamatthew]

Add GitHub Actions CI workflow with vitest setup

• Create test.yml workflow that triggers on PR to main

• Install Rust & Node.js in CI steps

• Add vitest configuration for frontend and backend

• Add test scripts using 'npm test' (vitest run)

• Add linting steps for code style consistency

• Configure cargo test for contracts

• Add sample tests to verify setup

• Fail workflow if any tests fail

• Add Prisma client generation step

• Configure DATABASE_URL for backend tests

• Use SQLite for test environment to avoid PostgreSQL setup complexity

• Ensure all tests pass in CI environment

The workflow now properly handles:
✓ Prisma client generation
✓ Database configuration for tests
✓ All test suites run successfully"

Acceptance Criteria:
✓ Workflow triggers on PR to main
✓ Steps to install Rust & Node
✓ Fails if tests fail

Additional Features:
✓ Linting steps for consistent code style
✓ Named 'CI / Validation' for clarity
✓ Uses vitest run via npm test
✓ Caches dependencies for faster runs"

this Closes #80

[ogazboiz]

hey, thanks for the contribution!

just had a look at this — the backend and frontend CI checks are currently failing and there are merge conflicts with main.

could you pull the latest changes, resolve the conflicts, and take a look at the workflow logs under the "Checks" tab to fix the failing steps?

once that's sorted let us know and we'll take another look — happy to help if you get stuck! if you want to contribute more or follow up if issues are open, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

[ogazboiz]

hey, thanks for the contribution!

To ensure your Pull Request passes the CI pipeline and maintains repository stability, please follow these technical requirements:

1. Backend Testing (Vitest)

• Version: We have standardized on Vitest ^2.1.8. Do not upgrade to v3 or v4 without explicit approval, as they introduce native dependency issues in the CI environment.
• Isolation: Each test file now runs in its own forked process (pool: 'forks'). This prevents vi.mock() and other module-level states from leaking between files.
• Prisma Mocking: When testing controllers, always mock the Prisma client in backend/src/lib/prisma.ts. Do not rely on a real database for unit tests.
• CLI Flags: Avoid using the --verbose flag in Vitest commands, as it is incompatible with the v2 CLI.

2. API Versioning & Routing

• Endpoints: Hit versioned endpoints (e.g., /v1/streams) instead of the deprecated root endpoints (e.g., /streams).
• Response Codes: Endpoints return 410 Gone for specifically deprecated routes. Ensure your tests handle these correctly.
• Input Validation: Controllers expect strict field names (e.g., streamId, ratePerSecond, depositedAmount). Use the types defined in src/services/ and src/controllers/.

3. Infrastructure & Dependencies

• Husky: The pipeline skips Husky. Your package.json scripts should use husky || true to prevent non-interactive shell failures.
• Prisma Generation: Always ensure your workflow runs prisma generate before tests. The CI now handles this in a consolidated "Setup Database" step.
• Native Bindings: If you add dependencies with native bindings (like Rollup or ESBuild), ensure they are compatible with the ubuntu-latest (linux-x64) runner.

4. Frontend Best Practices

• Directives: Always include "use client" at the top of components that utilize React hooks or browser APIs.
• Dependencies: Ensure all utilized libraries (like react-hot-toast) are explicitly added to frontend/package.json and not just inherited from the root.

Please make sure your CI passes before we finalize the merge. Let us know if you have any questions!

If you want to follow up or have questions, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

[ogazboiz]

hey, just checking in on this again — still waiting on those updates to fix the CI based on our last comment. no rush if you're busy, just let us know if you plan to continue with it or if we should close it for now!

if you want to contribute more or follow up if issues are open, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

[ekumamatthew]

Hi. Had issues with my pc and currently it's Bern fixed in a shop. If I have it, I'll looking and fix

[ogazboiz]

closing this due to no progress — totally understand the PC issues, those are rough! feel free to reopen whenever you're back and ready. main things to fix: resolve merge conflicts by rebasing on main, and get CI checks passing. we'll be happy to review again. join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0