fix: renaming duplication bug#20
Conversation
|
@mrpaaradox is attempting to deploy a commit to the ENRA doo Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
hey @AntonioErdeljac please have a look on the above pull request. |
As we don't return the existing metadata of the user, on renaming this allows the user to have 2 files of the same name on the same level which is actually against the rules of the file explorer.
We are trying to restricting the user by not allowing them to create 2 files with the same name on the same level. Hence while renaming too, it shouldn't be able to do so. Hence I have just returned the existing metadata so that Convex can easily block the user while reanaming.
PS: I am not sure if this PR get's merged or not but I did this because you are putting so much effort & hence I wanted to give this back to you showing that in times of AI, I am still learning from you & I care for all the efforts you made for the video ❤️