elevate-project routes updated

[Prajwal17Tunerlabs]

Summary by CodeRabbit

• New Features

  • Introduced a new POST API endpoint at /project/v1/userExtension/update to enable updating user extension details within the Project service. This adds broader API coverage without impacting existing routes or behavior. No breaking changes.

• Chores

  • Bumped package version to 1.1.50 to reflect the new endpoint availability.

[coderabbitai]

Walkthrough

Adds a new POST route mapping for /project/v1/userExtension/update in elevate-project/constants/routes.js and bumps package version from 1.1.49 to 1.1.50.

Changes

Cohort / File(s)	Summary of Changes
Routing: Add userExtension update route elevate-project/constants/routes.js	Appends a new route object for POST /project/v1/userExtension/update with inSequence: false, orchestrated: false, targeting the same path/method under service "project".
Version bump elevate-project/package.json	Increments version from 1.1.49 to 1.1.50.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant C as Client
  participant G as API Gateway/Router
  participant P as Project Service

  C->>G: POST /project/v1/userExtension/update (body)
  Note right of G: Route config: inSequence=false, orchestrated=false
  G->>P: Forward POST /project/v1/userExtension/update
  P-->>G: Response (status, payload)
  G-->>C: Response propagated

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• project usercourses routes added #331: Adds a POST route to the same routes array for a different "project" endpoint (userCourses).
• added-routes-for-project-survey #338: Introduces additional route entries in elevate-project/constants/routes.js.
• elevate-project routes updated #337: Adds another POST route entry to the same exported routes array.

Suggested reviewers

• VISHNUDAS-tunerlabs

Poem

A rabbit taps the router’s slate—
New path burrows, swift and straight.
POST hops in without a queue,
No orchestration—clean and true.
Version ticks with gentle cheer,
Another trail is crystal clear. 🐰✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly indicates that the elevate-project’s routing configuration has been modified, directly reflecting the core change of adding a new route entry in the routes array.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/utils-routes-update-3

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 70de43f and b902046.

📒 Files selected for processing (2)

• elevate-project/constants/routes.js (1 hunks)
• elevate-project/package.json (1 hunks)

🔇 Additional comments (2)

elevate-project/package.json (1)

3-3: LGTM!

The version bump from 1.1.49 to 1.1.50 is appropriate for adding a new route configuration.

elevate-project/constants/routes.js (1)

3274-3284: Confirm ID-parameterized variant for /project/v1/userExtension/update.
Most update routes include both non-parameterized and :id variants; please confirm whether /project/v1/userExtension/update/:id should be added.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}