yamankatby / firebase-extensions

A collection of Firebase Extensions designed to help you build better apps faster.

Hi there 👋

I build 🌐 websites and 📱 mobile apps — 🤖 Android and 🍎 iOS — with coffee and love.

• 🌱 I’m currently learning ...
• 👯 I’m looking to collaborate on ...
• 🤔 I’m looking for help with ...
• 💬 Ask me about 🧑‍💻 JavaScript ecosystem, ☁️ Google Cloud Platform, 🔥 Firebase
• 📫 How to reach me: 📧 [email protected], 📽 youtube.com/@react-native, 🐦 twitter.com/yamankatby
• ⚡ Fun fact: I started coding by reading a 1500-page book - I didn't learn anything from it.

Also, check out my 🔗 LinkedIn and 💬 StackOverflow profiles or find me in your terminal npx yaman.

firebase-extensions's Issues

Update `firestore-one-to-one` extension PREINSTALL.md

Handle more than 500 operations on firestore-connect ext batch write

Right now if the src document changes, it updates all the target documents with a batch transaction.

What if I have more than 500 target documents?

A batched write can contain up to 500 operations.

From docs: https://firebase.google.com/docs/firestore/manage-data/transactions#batched-writes

Update the `firestore-one-to-one` extension example in the `example` fields of the extension params

👇

firebase-extensions/firestore-one-to-one/extension.yaml

Line 104 in 5be4b5a

example: countries

firebase-extensions/firestore-one-to-one/extension.yaml

Line 112 in 5be4b5a

example: capitals

firebase-extensions/firestore-one-to-one/extension.yaml

Line 120 in 5be4b5a

example: capitalId

Update `firestore-one-to-one` extension POSTINSTALL.md

Migrate to Nx?

It's faster and also Lerna is built on top of it ??!! why not?

Add support to more emoji styles

Styles to support

• #38
• #39
• #40
• #41
• #42

Support Arrays in Source Field

Can this app be updated to support array fields as a source, too?

If some of the shared properties are not exists in the source document, continue syncking the existing ones anyway

A more explicit example of the `firestore-one-to-one` extension

💡

The Country/Capital example is not an example that can explain the extension easily, find some more explicit examples for the extension.

🗺️ Roadmap

• #49
• #50
• #51

Planning `analytics-slack-notifier`? extension

Basically, whenever an event (specified by the user) is logged in Firebase Analytics (Google Analytics for Firebase) the extension will be triggered to send a message (notification) to the slack channel (specified by the user).

The trigger function:

functions.analytics.event('in_app_purchase').onLog((event) => {
  // Send the notification message to the user-specified channel in Slack. 
});

Note The example from https://firebase.google.com/docs/analytics/extend-with-functions

Here's an example of using slack API in cloud functions, which might be helpful 👉 https://github.com/firebase/functions-samples/tree/main/github-to-slack

What next?

• What the message (notification) would say? 🤔
• What about Pub/Sub messages? maybe a separate extension 👉 https://www.youtube.com/watch?v=hd9FQOlI2Ts&ab_channel=Firebase

Add Eventarc events support

• #33
• #34
• #35

Add the demo videos to the main README.md?

Add Eventarc events support to the `generate-og-image` extension

Add Backfill function to the `firestore-connect-document` extension

Make the both documents in the One-to-One relation have the same uid

Update the project structure to have the tests and emulators inside each extension

Add PDF file support

Add support to `Fluent Emoji` emoji style

Add support to `OpenMoji` emoji style

Remove the TOC from the `firestore-connect-document` extension README

Fix Cloud Function memory size

Support reference value as a source id

Add Eventarc events support to the `firestore-connect-document` extension

Create a new video for the `firestore-one-to-one` extension using the new example

Add support to `Blobmoji` emoji style

Planning `firestore-one-to-many` extension 🧠

Implements the one-to-many relationship between Firestore collections.

Params 🛠️

Target Collection Path

The path to the collation containing the documents represents the first side of the relation, the "one" side.
Example: authors

Destination Collection Path

The path to the collation containing the documents represents the second side of the relation, the "many" side.
Example: books

Target Ref Field Name

The name of the field in the destination collection that contains the reference of the document in the target collection.
Example: authorId

Destination Ref Field Name

The name of the field in the target collection where the id of the destination document will be stored.
Example: bookId
Default: id

Target Data Field Name

The name of the field in the target document where the list of the destination documents will be stored.
Example: books

Destination Data Field Name

The name of the field in the destination document where the data from the target document will be stored.
Example: author

Fields to copy from the target collection

A comma-separated list of field names to copy from the target collection to the destination collection.
Example: name,biography

Fields to copy from the destination collection

A comma-separated list of field names to copy from the destination collection to the target collection.
Example: title,summary

Target document deletion behaviour

What should happen to the documents in the destination collection when a related target collection is deleted?

Create templates collection in the onInstall lifecycle function

Use user-friendly descriptions for parameters

Add Eventarc events support to the `firestore-one-to-one` extension

Add support to `Noto Emoji` emoji style

Update `firestore-one-to-one` extension README.me

Delete `System default` emoji provider and make the extension defaults to `Twimoji`

Add optional templates editor UI?

Make image export options at the document level

Update `firestore-one-to-one` extension documentation

🚗 Roadmap

• #43
• #44
• #45
• #48

Add an example to the description in the README of the `firestore-one-to-one` extension

Update `generate-og-image` extension docs

• Write PREINSTALL and POSTINSTALL docs.
• Update the README.md to mirror the new changes.

Add Backfill function

The Backfill function is an onInstall lifecycle event handler, which will run after installation is completed and handle the sync process for the existing documents.

Furthur disccustion

• Shoud it be onInstall or onConfigure?
  • If onConfigure what should happen to the previous documents?

Progress

• #36
• #37

Add support to `Fluent Emoji Flat` emoji style

Extensions require Apache 2.0 headers in all source code files

Submitted extensions will require the following header in all source code files, to be covered by the Apache 2.0 license:

/*
 * Copyright 2019 Google LLC
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *    https://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

EDIT: let me double check this and get back to you :)

Add Backfill function to the `firestore-one-to-one` extension

Remove the Template param?

Error installing OG Image Generator extension in Firebase

When installing the extension using the default configuration in region europe-west3 (or europe-west2, or us-central1), I get the following error:

; RESOURCE_ERROR at /deployments/firebase-ext-generate-og-image-1/resources/onInstall: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"400","ResourceErrorMessage":"Build failed: npm ERR! Cannot read property 'chrome-aws-lambda' of undefined\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /www-data-home/.npm/_logs/2023-05-11T06_25_39_232Z-debug.log; Error ID: beaf8772"}; RESOURCE_ERROR at /deployments/firebase-ext-generate-og-image-1/resources/api: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"400","ResourceErrorMessage":"Build failed: npm ERR! Cannot read property 'chrome-aws-lambda' of undefined\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /www-data-home/.npm/_logs/2023-05-11T06_25_39_916Z-debug.log; Error ID: beaf8772"}

Tapping "retry installation" completes without another error, however the functions have "Error in Deployment" against them, so the install isn't actually successful.

Planning `firestore-chatgpt-?` extension 🧨

An extension to get the power of ChatGPT to your Firebase project.