[FEAT]: Implement System Logs Routes

[coxmars]

Implement System Logs API Route

Description

Create API routes for system log operations with Prisma + Zod validation. Follow existing patterns for routes, error handling, and database optimization.

---

Requirements

API Route

• Create src/app/api/(logs)/logs/create/route.ts → POST endpoint
• Follow existing grouped route structure (logs)
• Use consistent imports & method handling

Validation

• Add Zod schema → src/components/modules/logs/schema/system-log.schema.ts
• Required: action, description
• Optional: user_id, entity_type, metadata (JSON)
• Follow auth/schema/ style

Database

• Use @/lib/prisma + handleDatabaseError
• Implement SystemLog with Prisma ORM
• Use indexes: user_id, entity_type, created_at

Components

• src/app/api/(logs)/logs/create/route.ts
• src/components/modules/logs/schema/system-log.schema.ts

Validations

• Log created with POST
• Required + optional fields validated
• metadata accepts JSON
• created_at set automatically
• Indexes used for performance
• Response matches project standards

Tests

• Creation → valid payload creates SystemLog
• Validation → invalid returns 400
• User reference → user_id links correctly
• Metadata → stored/retrieved as JSON
• Error handling → consistent with other APIs
• Index performance → queries use indexes
• Response format → correct structure

⚠️ Please follow the guidelines for requesting an issue, launching commits, and describing PRs. Otherwise, they will be ignored. ⚠️

[Cedarich]

Hi,

I’d like to apply for the task of implementing the System Logs API route. With my experience using Prisma, Zod, and building clean, well-structured APIs, I can deliver a reliable endpoint that follows the project’s existing patterns for validation, error handling, and performance.

I’ll create the POST /logs/create endpoint with proper validation using Zod schemas, handle database operations with Prisma, and ensure consistent error handling. The solution will support optional fields like user_id and metadata while maintaining clean indexing for efficient queries.

My focus will be on building a stable and scalable logging endpoint that integrates smoothly with the current architecture and provides accurate, well-structured responses.

Recommended by OnlyDust for high-quality and dependable contributions.