In the process of developing a new web app front-end using the Appwrite SDK as backend, the SDK was updated from 18.0.0, which I started development with, to 20.0.0, the latest. I updated the project packages in reaction to last week's NPM's package's malware attackes. So I noticed all my local API endpoint calls to Appwrite were deprecated. And many of the Model interfaces I was using were unavailable in the latest package. Since the app is new and still in development, I decided to simply update all the Appwrite dependent code. However, to my surprise, all new CRUD APIs are marked as deprecated as well. It is a real pain to have to try to work with deprecated methods as there is a lot of TS and ESLint noise to deal with. Why are these just-released as of a couple of months ago APIs marked as deprecated? Is there a work-around?
It's because in 1.8 there is some renames, Databases is now TablesDb, and all methods names changed.
You can check it here:
https://appwrite.io/docs/references/cloud/client-web/tablesDB
Renaming your class and methods will remove the warnings
Recommended threads
- 1:1 relationship doesn’t sync after re-a...
Hi, I’m trying to use a two-way one-to-one relationship. It works fine when I create a record with the relationship set, and it also works when I unset it. But ...
- Failed to create function
Hey everyone 👋 I'm having an issue creating Functions on Appwrite Cloud and I'm not sure if it's a platform bug or something wrong in my project. When I try t...
- Upsert with setting permissions
Hi there, I am using self-hosted appwrite v1.7.4 and trying to use the bulk update stuff that was released with 1.7.x. Unfortunally I found that there is an ser...