Intro-To-Bug-Hunting VS sdk-generator

if you want to learn bug bounty hunting from scratch, enjoy it; all content will be update as soon (: https://github.com/nabasteh/intro-to-bug-hunting

Unit tests for the Android and Kotlin SDKs

In case you discover any bugs/issues, want to share suggestions, or make contributions to the .NET SDK, please visit Appwrite’s SDK Generator repository on GitHub.

There is some community work on the Go SDK! If you're willing to help you can check this issue: https://github.com/appwrite/sdk-generator/issues/8

nothendev posted on Oct 21, 2022

However, we have new PR ready for supporting bytes in both i/o and web platforms that will allow us to support 5.0mb+ file uplods in Web platforms as well using bytes which you can check here https://github.com/appwrite/sdk-generator/pull/451

Fixed deploy function JSON parse error

I was about to ask how you manage to support so many different language bindings, then I noticed that you’ve built an ‘SDK generator’ [1]. Very cool! I’ve not come across this concept before - how does it work?

[1] https://github.com/appwrite/sdk-generator

There is a whole repository for Appwrite SDK generator that helps any developer prepare SDK for any programming language. This tool helps keep all SDKs up to date with Appwrite features and easily fixable if there is some new error introduced by a new language version.

Welcome to Day 22 👋. For a really long time, we found ourselves having to set up an SDK to quickly test some new functionality, so we decided to build ourselves a CLI! We wanted to stay agnostic to the technology used so we decided to go with a Docker approach. Appwrite CLI is packaged as a Docker container, so the only dependency you will ever need is Docker 😊. The CLI is generated automatically using our Swagger specification and our very own SDK generator.