-
Notifications
You must be signed in to change notification settings - Fork 543
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
All mutations need to have toast.error #2225
Comments
I plan to work on this if it gets approved. Please don't assign yourself |
don't try to reserve this please, it's unfair to others, |
I can't reproduce it |
I got the reason why it's happening. It's because I was trying to rename it to a name that already exists. ( I didn't know that if I use a name in SDK initialization without having a namespace it creates one automatically ) But the toast problem still exists then |
that's not the SDK, but the API where this happens. OK so the issue is renaming when the new name collides with an existing one. We need to return a better error from trpc and make the toast work also there seems to be no loading indicator on the save button |
/award 150 |
Awarding harshsbhat: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/harshsbhat |
/assign |
Assigned to @Vardhaman619! Please open a draft PR linking this issue within 48h |
/assign |
Assigned to @harshsbhat! Please open a draft PR linking this issue within 48h |
I have unassigned. Its open if anyone wants to take it |
/assign |
You already have an open issue assigned to you here. Once that's closed or unassigned, only then we recommend you to take up more. |
@AkshayBandi027 I unassigned myself so that someone without any issue in hand can work on this. Please |
/assign |
Assigned to @harshsbhat! Please open a draft PR linking this issue within 48h |
assigning this as my work in the other PR is done and just needs a few reviews |
@chronark as I was solving this. I noticed there are multiple mutations where if they fail we are not logging a proper error message using the toast. Which means that the user won't get a success/error toast and the action won't take place either. I have listed the exact mutations here. Wdyt? Should we update this issue to solve the following too?
|
yes please |
@Vardhaman619, Just a little reminder: Please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12h, you will be unassigned automatically. |
@Vardhaman619, Just a little reminder: Please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12h, you will be unassigned automatically. |
Preliminary Checks
I have reviewed the documentation: https://unkey.com/docs
I have searched for existing issues: https://github.com/unkeyed/unkey/issues
This issue is not a question, general help request, or anything other than a bug report directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.
Reproduction / Replay Link (Optional)
No response
Issue Summary
I noticed there are multiple mutations where if they fail we are not logging a proper error message using the toast. Which means that the user won't get a success/error toast and the action won't take place either. I have listed the exact mutations here.
Steps to Reproduce
Expected behavior
It should rename the namespace and display a proper toast message.
Other information
No response
Screenshots
Version info
The text was updated successfully, but these errors were encountered: