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

Fixed the Toast message and changed the routing for DeleteOrg page. #1114

Closed
wants to merge 0 commits into from

Conversation

AmitSharma512
Copy link
Contributor

What kind of change does this PR introduce?

This PR solves the issue of the toast message not being displayed while deleting the organization.

Issue Number:

Fixes #1108

Did you add tests for your changes?

No

Snapshots/Videos:

After Fixing the issue :

After.fix.mp4

Summary

Previously, When we delete an organization or a sample organization, no toast message of success was shown, and instead of using React Routing, window.location.replace was used. This PR solves the all above issues.

Does this PR introduce a breaking change?

No

Have you read the contributing guide?

Yes

Copy link

github-actions bot commented Dec 2, 2023

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

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

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.

Copy link

codecov bot commented Dec 2, 2023

Codecov Report

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

Comparison is base (dec5042) 94.21% compared to head (d72514d) 94.21%.

Files Patch % Lines
src/components/DeleteOrg/DeleteOrg.tsx 12.50% 7 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1114   +/-   ##
========================================
  Coverage    94.21%   94.21%           
========================================
  Files          138      138           
  Lines         3282     3283    +1     
  Branches       912      912           
========================================
+ Hits          3092     3093    +1     
  Misses         183      183           
  Partials         7        7           

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

Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

Please make the code coverage 100% for the modified file. It has been declining overall and we need to make sure we get it back up to make our code more stable

Comment on lines 37 to 43
try {
await removeSampleOrganization();
toast.success('Successfully deleted sample Organization');
history.push('/orglist');
} catch (error: any) {
toast.error(error.message);
}
Copy link
Member

Choose a reason for hiding this comment

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

Please write the test for these lines.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried to write the tests, but every time I got an unexpected error that I was not able to solve.
According to my knowledge, my basics are correct but then also tests are not passing.

Comment on lines 51 to 52
toast.success('Successfully deleted Organization');
history.push('/orglist');
Copy link
Member

Choose a reason for hiding this comment

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

Please write the test for these lines.

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