refactor(backend): refactor middleware stack for composability and te…#415
refactor(backend): refactor middleware stack for composability and te…#415vstudio79 wants to merge 2 commits into
Conversation
…st coverage - Extract inline trace middleware from index.ts into dedicated trace.ts - Extract inline cache-control middleware into dedicated cache-control.ts - Create compose.ts utility for async-safe middleware composition - Create barrel index.ts exporting all middleware from single entry point - Refactor deprecation.ts to use structured pino logging (instead of console.warn) - Refactor session.ts to use AppError for centralized error handling - Create comprehensive test files: requestId, errorHandler, session, slaTracking, validate, requireFlag, idempotency, compose, trace, cache-control - Each middleware now has single responsibility with centralized error handling
|
@vstudio79 is attempting to deploy a commit to the smartdevs17's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@vstudio79 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Resolve conflicts in backend/src/index.ts: - Keep both traceMiddleware and correlationMiddleware/httpLogger - Remove console wrapping (per main branch) - Keep cacheControlNoStore after sessionMiddleware
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 15742864 | Triggered | Generic Password | a8f1ef7 | .github/workflows/migrations.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
1 participant
Closes: #364