757 results found
-
Firestore Index Name
As a Firestore project grows, so do the number of Composite Indexes.
While the fields are visible, being able to name a composite index would allow us to define which specific feature(s) a composite index is tied to, allowing us to remove unused indexes if they're no longer relevant.
9 votes -
should be able to sort data and select data with criteria on different fields
should be able to sort data and select data with criteria on different fields (the limitation section on https://firebase.google.com/docs/firestore/query-data/order-limit-data?hl=en&authuser=0)
2 votes -
11 votes
-
Add Bulk User Update to SDK
Add a bulk update user method to avoid handling the user configuration update limit of 10/s in code. Specifically, my use case is to bulk disable/enable users in a single call.
1 vote -
1 vote
-
HTTPS Proxy with Authentication
Firebase currently does not have a clear way of supporting HTTPS proxy. If the network is limited by OEM's restrictions, or firewalls then Firebase Crashlytics won't operate. Probably no Firebase service will be able to work.
We can set the domain and the port for HTTP proxy, but then it is not authenticated.
3 votes -
Support hierarchical google-services.json
When you define multiple build types for your application you need to create a google-services.json file for each build type, eg : app/src/flavor1, app/src/flavor2, app/src/flavor_3
This becomes cumbersome when using multiple build flavors. It would be great if
1. the flavor directories acted as optional overrides of a default
2. the hierarchy for google-services.json respected initWith, e.. if I create a buildType1 with "initWith debug" I should be able to use the debug/google-services.json unless I try to overwrite it.4 votes -
Expose subcollections as json fields
Currently, subcollections are treated separately from fields in the UI. This seems like an arbitrary distinction - a subcollection is simply a json object under a document. You could do the same thing with a string field.
The API could support retrieving subcollections as string fields in json format for a document. This would prevent the need to iterate over every document in a collection, then get a list of the subcollections, then retrieve the documents from those subcollections, etc. If worried about time required, since Firestore supports 100 nesting levels, perhaps the API call could include the nesting level…
1 vote -
Put the button to run a query on bottom not top in the console's query builder
In the console, after building a query in the query builder, one has to scroll up again and again to run it, it's an inconvenience when the query is long and has to be changed multiple times.
Putting the button at the bottom can make it easier to change and test out queries2 votes -
TTL for Realtime DB
Realtime DB is very similar to Redis functionality. It would be very valuable to enable real caching behaviour by adding time to live to an entry.
11 votes -
Allow security rules to validate custom bearer tokens
Currently, Firestore and Cloud Storage security rules
req.authproperty will only validate and accept Google-signed ID tokens from Firebase Auth/Identity Platform.This means that "user authentication rules" CANNOT be used if we rely on our own (or 3rd-party) authentication/token server.
Proposal:
Allow security rules to configure the token verification rules so that they can verify the token claims of a configured token authority. For example, tokens signed by a service account private key, or 3rd party auth server (aside from Firebase Auth/Identity Platform).1 vote -
firebase framework sveltekit environment (vite mode mode)
in a svelte-kit app if you have multiple environments (staging, production) you can specify multiple .env files.
Unfortunately, there is no way to tell Firebase which one to use so it always deploys using production. and always uses development in the emulator
3 votes -
Fix the spacing between the public messaging key and the date, so we can see and copy the entire public key.
We can never see the entire public key to know whether we are copying the entire key in the messaging section of the firebase console. Please fix.
1 vote -
1 vote
-
GODOT implementation
would be great if I could use the GODOT game engine with Firebase.
because I saw many other game engines use Firebase, like Unity I think will be great to have this feature.3 votes -
Query language (like SQL) but for firestore to enable developers to share queries across the whole stack
let's say that you have a Kotlin android app, Swift iOS app, a Dart Flutter app and cloud functions written in typescript.
there should be a way to re-use shared queries across the whole stack.
having a query language like SQL and pass those redundant queries across all apps that would be really efficient and could save developers a lot of time and it could produce less bugs.I'm not suggesting SQL, I'm suggesting to have a query language that's all.
1 vote -
Support yarn and/or pnpm for frameworks
Currently frameworks only used npm
This can cause issues if using yarn or pnpm, and npm does not read the lockfile and you can end up with different versions of dependencies in production
Deployments with frameworks should detect the package manager used
3 votes -
I am not able get server key
Why it is Disabled?
3 votes -
Shorten email verification link
I am building a web application using Firebase authentication. I require email verification to have users access our platform. Currently, the link is quite long, but I was wondering if there was any way to shorten the URL to make it more user friendly, and to make it look less spam-like
3 votes -
Rule change history for Storage
Firestore tracks the history of changes to security rules. Would be great to have the same for Storage and Realtime Database, too.
1 vote
- Don't see your idea?