Skip to content

Conversation

@amolsontakke3576
Copy link
Contributor

No description provided.

Signed-off-by: Amol Sontakke <[email protected]>
Copy link
Member

@lukaszgryglicki lukaszgryglicki left a comment

Choose a reason for hiding this comment

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

/lgtm

@amolsontakke3576 amolsontakke3576 merged commit a2b1561 into main May 28, 2025
9 of 10 checks passed
},
{
path: 'cla/project/:projectId/user/:userId',
path: 'cla/project/:projectId',
Copy link
Member

Choose a reason for hiding this comment

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

Please do not remove the old route which is our default route for almost all flows.
You should add a new route (without uuid) instead and for that route you should call /v2/user-from-session API and when you get user UUID from that API - redirect back to "old" route with that user UUID just returned from api, so:

On cla/project/:projectId call /v2/user-from-session to get user. Get this user's UUID and route to cla/project/:projectId/user/:userId. cc @thakurveerendras @amolsontakke3576 @mlehotskylf

import { ClaContributorService } from 'src/app/core/services/cla-contributor.service';
import { ProjectModel } from 'src/app/core/models/project';
import { UserModel } from 'src/app/core/models/user';
import { UserFromSessionModel, UserFromTokenModel } from 'src/app/core/models/user';
Copy link
Member

Choose a reason for hiding this comment

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

Similar here - I think you need to add two new models but don't remove the already exiting one...

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants