firebase-tools VS sdk-generator

And it seems to deploy on first try, but then I got a loop error. Turns out after posting a bug, and getting sent to GitHub, this is a known issue when deploying to Cloud Functions. The fix is to edit your server.ts file, and don't use the process.env['PORT'] variable, as it apparently is already in use.

See issue.

No, just JS. Have you tried this?

In this example, I am using NX monorepo. I have my Angular Universal as one application and cloud functions as another application. If you don’t use NX or even some time has passed since publishing this blog post, you may want to visit Integrate web frameworks with Hosting from Firebase, however, there is an existing issue on Unable to detect the web framework in use when using angular app within nx monorepo.

Support for Sveltekit SSR has been added https://github.com/firebase/firebase-tools/issues/5158

// https://github.com/firebase/firebase-tools/issues/1532 if (admin.apps.length === 0) { admin.initializeApp() } export const deleteAllUserJobs = functions.https.onCall(async (context: functions.https.CallableRequest) => { const uid = context.auth?.uid if (uid === undefined) { throw new functions.https.HttpsError("unauthenticated", "You need to be authenticated to perform this action") } const firestore = admin.firestore() const collectionRef = firestore.collection(`/users/${uid}/jobs`) const collection = await collectionRef.get() logger.debug(`Deleting ${collection.docs.length} docs at "/users/${uid}/jobs"`) // transaction version await firestore.runTransaction(async (transaction) => { for (const doc of collection.docs) { transaction.delete(firestore.doc(`/users/${uid}/jobs/${doc.id}`)) } }) logger.debug(`Deleted ${collection.docs.length} docs at "/users/${uid}/jobs"`) return {"success": true} })

This should be supported via our built-in NextJS support https://firebase.google.com/docs/hosting/frameworks/nextjs if you have troubles with this functionality, please file a bug over on github https://github.com/firebase/firebase-tools

Now that app directory is stable, we support it. Keep an eye on the firebase-tools changelog, we've actively working on things. https://github.com/firebase/firebase-tools/releases

The Firebase CLI, check out the release notes

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.