Fixes Organization Not Found in Left Drawer

[GlenDsza]

What kind of change does this PR introduce?

bugfix

Issue Number:

Fixes #1333

Did you add tests for your changes?

Yes

Snapshots/Videos:

Fixes.No.Org.in.Left.Drawer.mp4

Summary

After Login, Opening User profile generated no organization found error, and user profile opened through 'My Organizations' page used to render 'LeftDrawerOrg' which is meant to be rendered if user profile is opened from 'organization dashboard'.

• The issue is fixed by conditionally rendering LeftDrawerOrg Component if UserProfile is reached from organization dashboard and rendering LeftDrawer Component if UserProfile reached from 'My Organizations Page'

• Added basic CSS to highlight User Profile Option in Left Drawer if User Profile Page is open.

• Refactored (Simplified/Efficient) OrganizationScreen & SuperAdminScreen and their respective tests.

Does this PR introduce a breaking change?

No

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

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
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

[github-actions]

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

[Cioppolo14]

@GlenDsza Please fix the failing test application check.

[codecov]

Codecov Report

Attention: Patch coverage is 97.59036% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 97.64%. Comparing base (3601c92) to head (be9ce38).

❗ Current head be9ce38 differs from pull request most recent head 6b5aae7. Consider uploading reports for the commit 6b5aae7 to get more accurate results

Files	Patch %	Lines
src/screens/MemberDetail/MemberDetail.tsx	91.30%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1592      +/-   ##
===========================================
+ Coverage    97.61%   97.64%   +0.02%     
===========================================
  Files          157      157              
  Lines         3991     3954      -37     
  Branches      1201     1189      -12     
===========================================
- Hits          3896     3861      -35     
  Misses          89       89              
+ Partials         6        4       -2     

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

[palisadoes]

Please increase the code coverage of your patch so that the tests pass

[palisadoes]

NOTE Read very carefully

1. We just merged this PR which upgraded the prettier package.
   1. Upgraded prettier from 2.3.2 to 3.2.5 #1599
2. It reformatted over 150 files.

This will put your PR at risk of extensive merge conflicts. Do the following IN THIS ORDER:

1. upgrade your prettier in your local branch to the same version
2. run prettier on your local branch
3. update your local branch with the latest upstream

This will help to reduce the number of future merge conflicts for your PR.

[GlenDsza]

Hello @Cioppolo14 , PR is ready for review.

[GlenDsza]

I had a suggestion,

• the SuperAdminScreen.tsx and OrganizationScreen.tsx both act as container component for LeftDrawer.tsx and LeftDrawerOrg.tsx respectively
• but most lines of code are similar and serve the same purpose with minimal difference and are not being used anywhere apart.
• Maybe, we can merge both the files in one file (maybe called leftDrawerContainer) and rest handle the difference using minimal conditional logic

Actually I have worked already on this thing, if y'all agree should I Add the changes to this PR only or should create new issue and then create PR for it

[GlenDsza]

@palisadoes need reviews/reviewers for the suggestion and PR, so could then contribute to other issues

I had a suggestion,

• the SuperAdminScreen.tsx and OrganizationScreen.tsx both act as container component for LeftDrawer.tsx and LeftDrawerOrg.tsx respectively
• but most lines of code are similar and serve the same purpose with minimal difference.
• Maybe, we can merge both the files in one file (maybe called leftDrawerContainer) and rest handle the difference using minimal conditional logic

Actually I have worked already on this thing, if y'all agree should I Add the changes to this PR only or should create new issue and then create PR for it

[palisadoes]

Please fix the conflicting files

[GlenDsza]

@rishav-jha-mech @beingnoble03 Have resolved conflicts, added tests and addressed comments, need review

[Olatade]

@GlenDsza please can you update your branch with the latest changes.

[GlenDsza]

@Olatade Updated with latest changes

[beingnoble03]

nice work. lgtm.

@palisadoes not sure about the readme changes tho.

[palisadoes]

@GlenDsza

Your PR has too many unnecessary files that don’t relate to your issue.

REDAME.md

You can from the PR by running the commands below from the root directory of the repository

git add -u
git reset HEAD path/to/file
git commit

[GlenDsza]

@palisadoes @beingnoble03 Reverted changes made to README.md file, need approving review