-
Notifications
You must be signed in to change notification settings - Fork 988
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
Improve (Error) Notifications #89
Comments
I'm attaching the video to the comment because it doesn't autoplay above for some reason. Screen.Recording.2022-12-06.at.19.07.31.mov |
@asharonbaltazar This is something that I had in mind. Also, what do you think if we moved notifications to bottom right of the screen? |
Sounds about what I had in mind. Also, ack regarding the bottom-right positioning |
You can assign it to me. I don't think it'll take long to push something |
Can you please list all the instances where you want notifications created? |
Yes! I think these ones are the most important ones:
Feel free to implement anything else you think is useful! |
@mv-turtle Would you mind linking the respective functions mentioned in your comment above? I'd really appreciate that! |
Of course! I just updated the comment. Sorry for the wait |
Don't sweat it. I'll make another PR for these changes. |
@mv-turtle After looking at the code, I decided that, for now, it's probably best to avoid adding notifications until two things have been taken care of:
I believe both issues one and two can be solved by using a library such as React-Query. |
@asharonbaltazar Right, I think this makes sense! Indeed, React-Query looks great - seems like a very popular package. I can take a look at it soon-ish. Would you be interested in solving those 2 issues? Thank you for your help :) |
@mv-turtle While I appreciate the offer, this is a large feature that'll require many hours of work and collaboration, and I simply can't dedicate that much time. I'm not as invested in the project as Infisical members. I still have the |
Yes, don’t worry at all about this! Thank you so much :) |
Closing as stale and we have now a good error notification |
Feature description
It would be really great if notification auto-disappeared (e.g., a user had a notification saying that they have some duplicate keys and then it would disappear like int he attached example) so that they don't need to remove those themselves
The following is an example of how PostHog does. Ours doesn't need to be so well-animated, but I think this would an end goal :)
https://user-images.githubusercontent.com/78047717/206074042-f1b9c508-0993-4cc0-a33a-d7f0e3b3a1a2.mov
I also think that we generally have to add more notification (when secrets are saved, we should tell people something like "Successfully saved the secrets"). The auto-disappearence would be amazing in this case.
Why would it be useful?
It would a huge improvement for UX. I think many people would benefit from it.
The text was updated successfully, but these errors were encountered: