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.

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

Merging develop-userTypeFix in develop #1761

Merged
merged 46 commits into from
Mar 23, 2024

Conversation

AVtheking
Copy link

What kind of change does this PR introduce?

Feature

Issue Number:

Fixes PalisadoesFoundation/talawa-api#1965

Did you add tests for your changes?

Yes

Summary

Merging the develop-userTypeFix branch in develop.

Does this PR introduce a breaking change?
Yes

Have you read the contributing guide?

Yes

@AVtheking AVtheking requested a review from palisadoes as a code owner March 22, 2024 22:29
Copy link

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

@palisadoes
Copy link
Contributor

@AVtheking I'm going to close this PR. Use another source branch tests are going to fail

@palisadoes palisadoes closed this Mar 22, 2024
@palisadoes palisadoes reopened this Mar 22, 2024
function openDialogModal(redirectOrgId: string): void {

/* eslint-disable @typescript-eslint/explicit-function-return-type */
function openDialogModal(redirectOrgId: string) {
Copy link
Member

Choose a reason for hiding this comment

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

Make the function void and remove eslint-disable


function closeDialogModal(): void {
/* eslint-disable @typescript-eslint/explicit-function-return-type */
function closeDialogModal() {
Copy link
Member

Choose a reason for hiding this comment

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

Make the function void and remove eslint-disable

userData.user.userType === 'ADMIN' &&
userData.user.adminFor.length === 0)) ? (
(userData && adminFor.length === 0)) ? (
// eslint-disable-next-line
Copy link
Member

Choose a reason for hiding this comment

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

Remove eslint and wrap the complete div in <> </>

@@ -352,6 +359,7 @@ const Users = (): JSX.Element => {
</h4>
</div>
) : isLoading == false && usersData && displayedUsers.length === 0 ? (
// eslint-disable-next-line react/jsx-indent
Copy link
Member

Choose a reason for hiding this comment

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

Remove disable and wrap complete in <> </>

@palisadoes
Copy link
Contributor

@varshith257 It's failing

image

@palisadoes
Copy link
Contributor

@varshith257 Please fix the linting.

Copy link

codecov bot commented Mar 23, 2024

Codecov Report

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

Project coverage is 96.31%. Comparing base (9a64e7e) to head (b19d3ae).

❗ Current head b19d3ae differs from pull request most recent head 01a5f97. Consider uploading reports for the commit 01a5f97 to get more accurate results

Files Patch % Lines
src/screens/MemberDetail/MemberDetail.tsx 13.04% 20 Missing ⚠️
src/screens/UserPortal/Home/Home.tsx 70.90% 15 Missing and 1 partial ⚠️
src/screens/Users/Users.tsx 81.25% 3 Missing ⚠️
src/components/UsersTableItem/UsersTableItem.tsx 93.75% 1 Missing ⚠️
src/screens/OrgList/OrgList.tsx 85.71% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1761      +/-   ##
===========================================
- Coverage    97.94%   96.31%   -1.64%     
===========================================
  Files          178      178              
  Lines         4382     4447      +65     
  Branches      1259     1287      +28     
===========================================
- Hits          4292     4283       -9     
- Misses          86      155      +69     
- Partials         4        9       +5     

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

Copy link
Member

@varshith257 varshith257 left a comment

Choose a reason for hiding this comment

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

LGTM
Except low test coverage

@pranshugupta54
Copy link
Member

For MemberDetail page, I already have the re-designed page with 100% coverage. We can merge that first, currently this file has very bad coverage so instead of fixing it for old design we can use the new one.
Ref: #1667

@varshith257
Copy link
Member

@pranshugupta54 Okay, Thanks

@palisadoes
Copy link
Contributor

@pranshugupta54

  1. We have to approve the GitHub action because you've never merged a PR before. This is going to be time consuming and cause delays.
  2. Can you create a trivial PR in Admin that I can merge so that I don't have to approve subsequent workflows for you? For example add a space to a file

@palisadoes palisadoes merged commit 6bcb24c into PalisadoesFoundation:develop Mar 23, 2024
7 of 10 checks passed
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.

4 participants