elevate-project routes updated

[Prajwal17Tunerlabs]

Summary by CodeRabbit

• New Features

  • Introduced a new API endpoint: POST /project/v1/userExtension/update in the Project service for updating user extensions. The route is active across the platform, not sequence-bound or orchestrated, and aligns with existing project APIs. Improves API coverage for user extension management and is discoverable in route listings.

• Chores

  • Bumped package version to 1.1.50.

[coderabbitai]

Walkthrough

Adds a POST route /project/v1/userExtension/update to the project service in both the Node routes configuration and the interface routes map, and bumps elevate-project package version from 1.1.49 to 1.1.50.

Changes

Cohort / File(s)	Summary
Project service route config elevate-project/constants/routes.js	Adds a new route object for POST /project/v1/userExtension/update with inSequence: false, targeting the project service with the same path and method.
Interface routes mapping interface-routes/elevate-routes.json	Inserts corresponding route entry: source /project/v1/userExtension/update, method POST, priority: MUST_HAVE, inSequence: false, orchestrated: false, package: elevate-project, 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 Gateway/Router
  participant P as Project Service

  Note over C,G: New endpoint
  C->>G: POST /project/v1/userExtension/update
  G->>P: POST /project/v1/userExtension/update (inSequence: false)
  P-->>G: Response (success/error)
  G-->>C: Response forwarded

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• elevate-project routes updated #337: Also adds POST routes to the same exported configuration and interface routes, indicating coordinated routing updates.
• project usercourses routes added #331: Adds another POST route for the project service (different endpoint), showing a related pattern of route expansions.

Suggested reviewers

• VISHNUDAS-tunerlabs

Poem

I twitch my whiskers, routes align,
A POST hops in—precise, benign.
From gate to project, swift and straight,
No sequence queue, no need to wait.
Version bumped, the path is true—
I thump my paw: deploy, woo-hoo! 🐇✨

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 clearly indicates that the pull request updates the routing configuration for elevate-project, which aligns with the addition of a new POST route in the changeset. It directly references a real and central part of the modifications without introducing unrelated information. Although concise and relevant, it remains somewhat generic and could be more descriptive about the specific endpoint added.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

📜 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 5697371.

📒 Files selected for processing (3)

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

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-08-05T09:46:50.071Z

Learnt from: MallanagoudaB
PR: ELEVATE-Project/utils#329
File: elevate-project/constants/routes.js:0-0
Timestamp: 2025-08-05T09:46:50.071Z
Learning: In the elevate-project/constants/routes.js file, the `orchestrated` property is not compulsory for all route configurations. Out of 293 total routes, 33 routes (about 11%) exist without this property, making it optional rather than required.

Applied to files:

• interface-routes/elevate-routes.json
• elevate-project/constants/routes.js

📚 Learning: 2025-08-05T09:46:50.071Z

Learnt from: MallanagoudaB
PR: ELEVATE-Project/utils#329
File: elevate-project/constants/routes.js:0-0
Timestamp: 2025-08-05T09:46:50.071Z
Learning: In the elevate-project/constants/routes.js file, the `orchestrated` property is not compulsory for all route configurations. Many routes exist without this property, making it optional rather than required.

Applied to files:

• elevate-project/constants/routes.js

🔇 Additional comments (3)

elevate-project/package.json (1)

3-3: Version bump aligns with new interface contract.

The 1.1.50 bump cleanly communicates the new /project/v1/userExtension/update route exposure.

interface-routes/elevate-routes.json (1)

12663-12674: New route entry matches existing project patterns.

The POST /project/v1/userExtension/update mapping mirrors neighboring project routes (priority, sequencing, service binding), so it should wire through without surprises.

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

3275-3282: LGTM on the new userExtension route.

The mapping mirrors the target path/type and aligns with the surrounding route configurations. Nicely done.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.}