Port '/v2/user/<user-uuid>/active-signature' to golang

[lukaszgryglicki]

This is WIP do not merge yet.
cc @mlehotskylf @amolsontakke3576 @thakurveerendras

Summary by CodeRabbit

• Chores
  • Updated the service to use an improved API endpoint for retrieving a user's active signature.

[coderabbitai]

Walkthrough

The getUserActiveSignature method in the ClaContributorService was updated to use the V4 API endpoint instead of the V2 endpoint for retrieving a user's active signature. The method's logic and return type remain unchanged, with only the URL path being updated internally.

Changes

File(s)	Change Summary
src/app/core/services/cla-contributor.service.ts	Updated getUserActiveSignature to call the V4 API endpoint instead of V2.

Sequence Diagram(s)

sequenceDiagram
    participant Frontend
    participant ClaContributorService
    participant API_V4

    Frontend->>ClaContributorService: getUserActiveSignature(userId)
    ClaContributorService->>API_V4: GET /v4/user/{userId}/active-signature
    API_V4-->>ClaContributorService: ActiveSignatureModel
    ClaContributorService-->>Frontend: Observable<ActiveSignatureModel>

Loading

Possibly related PRs

• Switch to new api '/v4/project-compat/<uuid>' instead of '/v2/project/<uuid>' #450: Updates a different method within ClaContributorService to switch from V2 to V4 API endpoints.

Suggested reviewers

• mlehotskylf
• amolsontakke3576
• thakurveerendras

Poem

A hop from V2 to V4,
The endpoint changed, nothing more.
Signatures fetched with modern grace,
The code keeps up a steady pace.
With every leap the service grows,
As bunny wisdom always shows! 🐇

---

📜 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 8a0f6bc and 95ee14f.

📒 Files selected for processing (1)

• src/app/core/services/cla-contributor.service.ts (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

src/app/core/services/cla-contributor.service.ts (1)

Learnt from: lukaszgryglicki
PR: communitybridge/easycla-contributor-console#452
File: src/app/core/models/user.ts:22-41
Timestamp: 2025-07-15T05:34:28.048Z
Learning: In src/app/core/models/user.ts, the UserFromTokenModel uses camelCase property naming because it matches the format returned by the /v4/user-from-token API endpoint. This API response format cannot be changed, so the model properties must follow the API structure rather than the existing snake_case conventions used in other user models.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (1)

src/app/core/services/cla-contributor.service.ts (1)

78-81: Endpoint bumped to V4 – double-check payload & caller expectations

The path change itself looks fine, but please verify:

1. ActiveSignatureModel aligns with the V4 response schema (the v4 APIs sometimes use different property casing—see the retrieved learning about camelCase vs snake_case).
2. All consumers of getUserActiveSignature() are tolerant of any V4-specific status or error formats.

Adding/adjusting a stubbed unit test for this method will help surface mismatches early.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[lukaszgryglicki]

Thanks, will merge this after other PRs are approved & merged:

• BE part: easycla #4714.
• fx-gateway part: lfx-gateway #112.
• acs-cli part: acs-cli #1105.