Contexte, source de vérité et ambiguïté

Why is this broken?

This Jest test fails after the recent change to UserService.

Expected behavior:
- deactivated users should not receive password reset emails.

Actual behavior:
- the service still sends a reset email.

Use:
- UserService.ts
- PasswordResetService.ts
- user.service.test.ts

Find the root cause and propose the minimal fix.
Do not change the public API.

Fix this error.

Analyze this stack trace and the selected code.

Error:
TypeError: Cannot read properties of undefined (reading 'items')

Expected behavior:
If the order has no items, return an empty summary.

Constraints:
- Do not hide other data quality issues.
- Add a unit test for the missing items case.

Generate a new RefundService following the same structure as PaymentService.ts.

Use:
- the same logging pattern
- the same error handling style
- the same dependency injection approach
- Jest tests similar to payment.service.test.ts

Voici 18 fichiers, toute l’architecture, 3 anciennes versions, 2 logs non liés, et une vague demande.

Voici le service, le test qui échoue, la stack trace, et le comportement attendu.

PaymentService.ts
PaymentService.old.ts
PaymentService.experimental.ts

Follow the payment service style.

Use PaymentService.ts as the source of truth.
Ignore PaymentService.old.ts and PaymentService.experimental.ts.

Create RefundService.ts with the same dependency injection, logging, and error handling style.

export function calculateRiskScore(user: User): number {
  let score = 0;

  if (user.failedLoginAttempts > 5) {
    score += 20;
  }

  if (user.hasNewDevice) {
    score += 15;
  }

  return score;
}

Review only the selected function.

Goal:
Improve readability and make scoring rules easier to extend.

Constraints:
- Do not change current scoring values.
- Do not add demographic or protected attributes.
- Keep return type as number.
- Suggest unit tests.

Generate tests for UserService.ts.
Follow the style and naming conventions in user.service.test.ts.
Do not create a new test framework setup.

Use the API behavior described in README.md.
Update the selected endpoint implementation to match the documented response format.

Fix this.
Improve this service.
Make it secure.
Optimize this.
Rewrite this module.

Optimize this service.

Optimize this service to reduce database calls.
Preserve the response format and public API.
Identify repeated queries.
Suggest caching only if it does not introduce stale data risks.
Add tests or explain what tests should be updated.

Make it secure.

Review this Express route for authentication, authorization, input validation, SQL injection, sensitive logging, and unsafe error messages.
Return risks and recommended fixes.
Do not modify code yet.