Fixed login screen reappearing after successful login

[aarishshahmohsin]

What kind of change does this PR introduce?

This PR fixes the reappearing of the login page after successfully logging in as the SuperAdmin.

Issue Number:

Fixes #1328

Did you add tests for your changes?
No

Snapshots/Videos:

2024-01-10.15-14-46.mp4

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

No

Other information

This issue exists because the setting of the bearer authentication header happens only once in the src/index.ts file when the page is freshly loaded or reloaded.

const httpLink = new HttpLink({
  uri: BACKEND_URL,
  headers: {
    authorization: 'Bearer ' + localStorage.getItem('token') || '',
  },
});

So when we firstly load the login page and then redirect to the orglist page, the token does not get included in the header.

Therefore, I added the bearer token in the header with the request that was causing the error and hence the reload

  const {
    data: userData,
    error: errorUser,
  }: {
    data: InterfaceUserType | undefined;
    loading: boolean;
    error?: Error | undefined;
  } = useQuery(USER_ORGANIZATION_LIST, {
    variables: { id: localStorage.getItem('id') },
    // added code
    context: {
      headers: { authorization: `Bearer ${localStorage.getItem('token')}` },
    },
  });

This fixed the issue.

Have you read the contributing guide?
Yes

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (655b6b3) 92.77% compared to head (75c4105) 97.45%.
Report is 91 commits behind head on develop.

Files	Patch %	Lines
...rgProfileFieldSettings/OrgProfileFieldSettings.tsx	90.00%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1415      +/-   ##
===========================================
+ Coverage    92.77%   97.45%   +4.67%     
===========================================
  Files          134      138       +4     
  Lines         3238     3690     +452     
  Branches       904     1079     +175     
===========================================
+ Hits          3004     3596     +592     
+ Misses         225       89     -136     
+ Partials         9        5       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.