-
-
Notifications
You must be signed in to change notification settings - Fork 758
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
Toast Messages not working while Deleting Organization. #1108
Comments
@palisadoes I want to work on this issue |
We are now focusing on three types of issues as priority areas:
We will only be accepting feature issues for deficiencies that are obviously lacking in the apps. These are things that make it very difficult to operate the apps. Even so, the PRs will still require you to understand testing as stated before. Closing |
@palisadoes the code for the toast message is written in the code , but it is not working, I just fixed it so that the user can interact and the user can know what happened and the code is using windows.replace instead of using react routing like "Use history", |
Thanks for the clarification. I'll reopen and assign it to you. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Describe the bug
When we delete an organization or a sample organization, no toast message of success is shown.
To Reproduce
Steps to reproduce behaviour:
Expected behaviour
There should be a Toast message of success whenever we Delete an organization.
Actual behaviour
No Toast message is shown whenever an organization is deleted.
Screenshots
Before fixing :
https://github.com/PalisadoesFoundation/talawa-admin/assets/110725065/a6ce0fa6-9e3c-4841-865c-066d590b66b4
Additional details
I want to work on this issue.
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359
The text was updated successfully, but these errors were encountered: