-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
🐛 Bug Report: Server sdk for node deleteFile api delete storage bucket instead of file. #5310
Closed
2 tasks done
usamashafiqs opened this issue
Mar 31, 2023
· 4 comments
· Fixed by utopia-php/http#92 or utopia-php/http#96
Closed
2 tasks done
🐛 Bug Report: Server sdk for node deleteFile api delete storage bucket instead of file. #5310
usamashafiqs opened this issue
Mar 31, 2023
· 4 comments
· Fixed by utopia-php/http#92 or utopia-php/http#96
Labels
Milestone
Comments
you should probably raise this issue on sdk-generator or sdk-node |
Hi all this is my first contribution/PR, I have worked on this and raised a PR. Please review the PR. Thank you |
Hi @freefreeP , thank you for raising the PR, our team will review it soon! |
Btw, this is a problem in utopia-php framework due to how were matching routes. This PR should fix this problem: utopia-php/http#92 |
Closed
2 tasks
2 tasks
stnguyen90
added
the
product / storage
Fixes and upgrades for the Appwrite Storage.
label
May 30, 2023
This was referenced Jul 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
👟 Reproduction steps
Server sdk for node
deleteFile
api delete storage bucket if file ID had empty string as parameter.It should throw exception if file ID had empty string.
👍 Expected behavior
It should throw exception if file ID had empty string provided instead of file ID.
👎 Actual Behavior
Server sdk for node
deleteFile
api delete storage bucket if file ID had empty string as parameter.🎲 Appwrite version
Version 1.2.x
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: