Description: If a user tries to update the slug, and the slug already exists for another user, it displays an error with "something went wrong". In the back end, a prisma error occurs. New! The other problem is: if you change the slug, or any change in general tab, it saves successfully, in db is correct, but from an UI perspective, if you immediately switch to any other tab (Subscription, Account) and then come back to General, the previous version (before saving) is showed (probably cached). For example: i had a slug set as ducutest. changed it to ducu-test, db was correct, moved to subscription, came back, then it was showing again ducutest. Upon refresh, it showed ducu-test (correct value) Expected Behavior: We should handle the scenario on the back end, so that the prisma error doesn't occur. Optional: Jam.Link 1: Jam.Link 2:
0 votes
Vote to help us prioritize this feature
Sign in to join the discussion
Sign in