Skip to content

Conversation

@erseco
Copy link

@erseco erseco commented Nov 15, 2025

Summary

  • add a new nest-backend workspace with a minimal NestJS application mirroring the current API entrypoint
  • provide starter Users and Projects modules with in-memory storage for early contract tests
  • document how to bootstrap the NestJS service and ignore its build artefacts

Testing

  • not run

Codex Task

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +11 to +14
app.setGlobalPrefix('api/v2');
app.enableVersioning({
type: VersioningType.URI,
defaultVersion: '2'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid double /v2 prefix when enabling URI versioning

The bootstrap configuration sets app.setGlobalPrefix('api/v2') and also enables URI versioning with default version '2' while every controller is registered for version '2'. In NestJS the version segment is appended after the global prefix, so the effective routes become /api/v2/v2/users and /api/v2/v2/projects. The README states the service should be reachable under http://localhost:3000/api/v2, but those endpoints will 404 because they are mounted under /api/v2/v2/.... Either drop the hard-coded /v2 from the global prefix or disable explicit versioning to expose the endpoints at /api/v2/* as documented.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants