546 results found
-
31 votes
-
Having pure Dart SDKs for Firebase
Note: If your top priority is to use Flutter with Firebase on Windows/Linux, this may not be the best option.
Currently, the Flutter SDKs (also known as FlutterFire) are wrappers around other existing SDKs, such as the iOS, Android, and web SDKs. This allows Flutter apps to target these platforms when using Firebase. However, if a Flutter app needs to target other platforms, it is not possible. A pure Dart SDK would allow developers to target all the devices that Flutter supports, but they would need to manually customize the integration with Google Analytics in Firebase. This manual integration could…
28 votes -
28 votes
-
27 votes
-
Custom Claims Editor
Show Custom Claims and allow them to be managed in the Firebase Authentication Console (like in the Emulator). Usefull for manually creating the first super user, for example.
26 votes -
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.
26 votes -
26 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.
25 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
25 votes -
25 votes
-
DocumentReference join query
Please add a join query to Cloud Firestore. It seems that using DocumentReference for the join would be appropriate.
24 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.
23 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
23 votes -
22 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.
20 votes -
20 votes
-
Monorepo support
The current buildpacks used for Next.js in App Hosting can't seem to deploy monorepo setups.
I think it would be really useful if App Hosting supported this, especially since Next.js has great monorepo support via the
transpileModules
config option.19 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
19 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
18 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…
18 votes
- Don't see your idea?