752 results found
-
Better support for Cloud Tasks, e.g. queues
It is currently already possible to create google cloud tasks. However, this could be better integrated by creating an abstraction for queues, for example, which can also be monitored and controlled via the admin console and firebase emulator.
27 votes -
26 votes
-
Low-Latency Data Cache
Allow configurable caching of query results for reduced end-to-end latency and reduced resource pressure on underlying data sources.
25 votes -
Schema Creator Tool in the Firebase Console
Support creating GraphQL schema in the Firebase console
25 votes -
App Distribution should have at least basic management of email notifications
There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.
24 votes -
Add a Preview environment for App Hosting deployments.
As a developer, I want to be able to deploy my Next.js web app hosted using App Hosting to a Preview "channel", similar to
firebase hosting:channel:deployin hosting.
Thanks.24 votes -
Integrate with Row Level Security (RLS)
Allow clear integration with Postgres's RLS while defining access permissions.
24 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…
24 votes -
24 votes
-
24 votes
-
Automatic Deployment of Changed Firebase Functions
Firebase should offer a built-in feature to automatically detect changes to Cloud Functions and deploy only those functions, grouped into manageable batches to avoid rate limits. This feature would streamline deployments by:
- Scanning the project directory to identify functions with modified code since the last deployment.
- Automatically batching the deployment of changed functions based on rate limit thresholds (e.g., 8-10 functions per batch).
- Handling the deployment process transparently within the Firebase CLI or CI/CD integrations, reducing manual intervention.
This functionality would save time, minimize deployment errors, and improve developer workflows, particularly in large projects with numerous functions.
23 votes -
23 votes
-
Allow String to Timestamp conversion in Firestore rules
In Firestore rule, it could be very powerful to convert String containing date to Timestamp. For example, the RevenueCat extension store date as ISO 8601 string and we can't use them in firestore rule because date are not Timestamp.
In my Firestore rule, I would like to do something like :
timestamp.parse(collection.data.expires_date) > request.time
22 votes -
Support geographic area and proximity searches with PostGIS
Add GeoPoint and GeoBox scalar types and enable rich geo searching queries including indexing, "search within area", "find closest to point within radius", etc.
21 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
21 votes -
21 votes
-
Connectors with Admin-Only Access
Create sets of reusable operations that are not accessible from client applications but can be called from server code or manually in the Firebase Console.
20 votes -
Filter on reference fields in the Firestore panel
There is currently no way to filter on reference fields in the Firestore panel of the Firebase console.
20 votes -
FieldValue.min() and FieldValue.max()
Currently the Firestore API supports FieldValue.increment() to atomically increment or decrement a numeric value. I propose to add:
FieldValue.max(value): if the provided value is greater than the existing value on the server, then the field on the server takes this value. If it is less than the existing value, then the existing value remains.
FieldValue.min(value): (the opposite) if the provided value is less than the existing value on the server, then the field on the server takes this value. If it is greater than the existing value, then the existing value remains.
These operators should work on numeric fields AND…
20 votes -
20 votes
- Don't see your idea?