Skip to content

Conversation

@kartik-579
Copy link
Member

@kartik-579 kartik-579 commented May 17, 2023

Description

Updated status code for role fetch api to avoid FE redirection for 401 status code.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@kartik-579 kartik-579 merged commit 22e01d2 into main May 17, 2023
@kartik-579 kartik-579 deleted the status-code-change-role-api branch May 17, 2023 10:38
gireesh-naidu pushed a commit that referenced this pull request Jun 16, 2023
* chore: Updated Github ISSUE-TEMPLATE (#3390)

* Update bug.yaml

* Update feature.yaml

* updated status code for role fetch api to avoid FE redirect (#3395)

---------

Co-authored-by: Prakarsh <[email protected]>
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