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
- Storage Chunk upload bug
Hi, I'm experiencing an issue with Appwrite Storage chunked uploads. Small files upload successfully, but larger video files that require chunking fail. For ...
- Realtime Error Invalid query: Syntax err...
I was test driving Self-Hosted Appwrite for my use with Swift IOS apps as a backend while back and after successful trials, I started to move to incorporate int...
- listRows result parsing issue
I'm using Appwrite Dart SDK "24.2.0". When I perform a listRows call in dart, I have this reponse in JSON: in " Future<models.RowList> listRows()" { "total" :...