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
- How to Display File in Web?
I'm trying to use Appwrite's Storage to store images and display them in my app, however when I use the `getFileView`, `getFileDownload` or `getFilePreview` met...
- Project Paused Despite Daily Active Usag...
I noticed that my project was automatically **paused**, even though it is actively being used. The project is an **attendance application** that is used daily b...
- Sudden CORS Errors - Domain hasn't Chang...
I have an Appwrite project with two web apps configured, the first one has the hostname `*` and the second one I just added to test if it could fix the issue wi...