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

Use Better Error Handling and improve UI #1310

Closed
4 tasks done
ak-0404 opened this issue Oct 8, 2024 · 2 comments
Closed
4 tasks done

Use Better Error Handling and improve UI #1310

ak-0404 opened this issue Oct 8, 2024 · 2 comments

Comments

@ak-0404
Copy link
Contributor

ak-0404 commented Oct 8, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Feature Description

Instead of throwing an error like the current code does, we can display a more user-friendly message in the UI.
Please assign this issue to me, thank you!

Use Case

This feature enhances the project by improving how users interact with the system.
Users get informative and user-friendly messages when issues arise (e.g., when a directory isn’t found or models fail to load). Instead of vague technical errors or blank screens, they can understand what went wrong and take action.

Benefits

By providing meaningful and user-friendly error messages (e.g., “Failed to load models” or “Directory not found”), users are less likely to get frustrated and more likely to understand the issue. This leads to smoother interactions and better overall satisfaction.

Add ScreenShots

No response

Priority

High

Record

  • I have read the Contributing Guidelines
  • I'm a GSSOC'24 contributor
  • I want to work on this issue
@ak-0404 ak-0404 added the enhancement New feature or request label Oct 8, 2024
Copy link

github-actions bot commented Oct 8, 2024

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions reach out to LinkedIn. Your contributions are highly appreciated! 😊

Note: I Maintain the repo issue twice a day, or ideally 1 day, If your issue goes stale for more than one day you can tag and comment on this same issue.

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.
We are here to help you on this journey of opensource, any help feel free to tag me or book an appointment.

Copy link

Hello @ak-0404! Your issue #1310 has been closed. Thank you for your contribution!

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