414 results found
-
DocumentReference join query
Please add a join query to Cloud Firestore. It seems that using DocumentReference for the join would be appropriate.
22 votes -
22 votes
-
Support Go in Cloud Functions
Go is much more efficient than Python or Js and should be the obvious choice for backend where performance is crucial
20 votes -
Crashlytics custom alerts
Crashlytics velocity alerting mechanism is very basic and it unfortunately generates a lot of false positive alerts. Support more advanced alarm settings
20 votes -
Create a context.auth (1st Gen) equivalent for 2nd Gen cloud function
1st gen cloud functions can access auth info via context.auth as described here: https://firebase.google.com/docs/database/extend-with-functions?gen=1st#accessing_user_authentication_information
But 2nd gen cloud functions is yet to have the same function.
19 votes -
onDisconnect for firestore (user presence)
https://firebase.google.com/docs/firestore/solutions/presence
We have a workaround by using Realtime Database, but if you don't work realtime databases in your app, this seems inefficient and cumbersome. I'd like to see a native method for Firestore that offers this functionality. Perhaps offer a onSnapshot.disconnect hook.
18 votes -
Allow Trending Stability Notifications via the Slack integration
I would like the option to be able to receive trending stability notifications via the slack integration
17 votes -
17 votes
-
17 votes
-
Support monorepo
Firebase functions does not support monorepo structures (NPM monorepo, NX, Turborepo) during deployment.
Firebase uses custom archive logic for functions packaging (https://github.com/firebase/firebase-tools/blob/127ca3fbf7549d6c0cdf12e89e4465de9dd2b7c9/src/deploy/functions/prepareFunctionsUpload.ts), which does not support internal packages deployment out of the box.
Github discussion: https://github.com/firebase/firebase-tools/issues/653
16 votes -
16 votes
-
16 votes
-
16 votes
-
Provide command to add testers to Tester groups via CLI
Currently, the Firebase CLI command can add testers to a Firebase App distribution project. But adding testers to a tester group can be done only manually on the Firebase portal. This becomes tedious for teams who maintain multiple tester groups and a large number of testers. Adding feasibility to mention to which tester group, the tester should be added in the Firebase add tester CLI command will make this process easier.
15 votes -
Allow updating multiple documents through a query
Many other databases have support for update queries, such as:
- Apply "x" update data to all docs matching "y" query
- Delete all docs matching "x" query
Maybe these queries would only count as 1 write per doc, as opposed to 1 read + 1 write. At the very least they would have better performance.
15 votes -
Password-protected preview domains
Squarespace has a featured for "site-wide password protection" which is useful for staging unlaunched websites for stakeholders to review. This would help guard against any potential leaks.
Figma also has a feature similar to this.
We currently have to create a custom express.js server with an authentication middleware, but this is undesirable for several reasons:
- We'd have to re-create all of firebase hosting's serving features (i18n fallbacks, redirects, pretty urls, etc.)
- We can't easily test endpoints that are proxied to Functions/GCR
15 votes -
15 votes
-
15 votes
-
Security Rules: unique() operator
I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.
Background:
At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.
Feature Proposal:
The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed…
14 votes -
Support TypeScript in Cloud Functions
It's a pain to have to configure a process to watch and transpile TypeScript files to use in the emulator. Firebase CLI should have built-in support for it both in the emulator (with automatic watching, or on-the-fly transpilation as I showed here https://github.com/firebase/firebase-tools/issues/5633#issuecomment-1622585432) and when deploying.
14 votes
- Don't see your idea?