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

Feature Request: Logout Confirmation Modal #998

Closed
skbhagat0502 opened this issue Oct 22, 2023 · 3 comments
Closed

Feature Request: Logout Confirmation Modal #998

skbhagat0502 opened this issue Oct 22, 2023 · 3 comments

Comments

@skbhagat0502
Copy link
Contributor

Increasing Access

Feature request details
Description:
Currently, the website includes a logout button to allow users to sign out. To enhance the user experience and prevent accidental logouts, I propose the implementation of a logout confirmation modal.

Benefits:
User-Friendly: Reduces the likelihood of accidental logouts.
Enhanced Security: Provides an additional layer of confirmation for sensitive actions.
Consistency: Aligns with modern web practices for user interactions.

Details:
Upon clicking the logout button, a modal should appear, asking the user to confirm their intention to log out. The modal should include a clear message such as "Are you sure you want to log out?" along with buttons for "Confirm" and "Cancel."

@github-actions
Copy link

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

@skbhagat0502
Copy link
Contributor Author

@palisadoes , Please assign me this issue.

@palisadoes
Copy link
Contributor

We are now focusing on three types of issues as priority areas:

  1. The improvement in the reliability of our code base. There are many issues created to test existing code. It is a good place to start if you want to understand the operation of various apps. When you submit PRs, we automatically check to see whether the code you submitted has been covered by testing and that each file meets the minimum standard level of the repository as a whole. You won’t be able to avoid understanding testing regimes to contribute to Talawa.
  2. The fixing of bugs and features that seriously hamper the user from using the application. The apps have various shortcomings. The most obvious ones are where the apps do not work as expected. For example buttons that don’t work, errors or messages that are not displayed to make the user understand what to do and many more. Think of any difficulty you have had in getting things working, there could be a bug there waiting for you.
  3. Coding of screens for issues created by our Contributor team based on our soon to be updated design guide. This may include updates to existing screens. Stay tuned, we expect these issues to be created during the first week of November 2023. @rishav-jha-mech is leading this process for the Talawa Admin project
  4. The creation of additional our updated documentation that helps with improving both the experience of the end user and the various GitHub contributors who support the development of our software. This would include user guides.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants