Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use the new data-service user endpoint instead of the legacy endpoint based on the GitLab user state. #3409

Open
lorenzo-cavazzi opened this issue Nov 26, 2024 · 0 comments
Open

Use the new data-service user endpoint instead of the legacy endpoint based on the GitLab user state. #3409

lorenzo-cavazzi opened this issue Nov 26, 2024 · 0 comments
Labels
Cooldown

Comments

@lorenzo-cavazzi
Copy link
Member

In the V2 components, we should use the new /user endpoint from the data-service to check whether the user is authenticated or not instead of the legacy state.stateModel.user that only checks against GitLab.

There is already a isLoggedIn property from the getUser endpoint.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Cooldown
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lorenzo-cavazzi