741 results found
-
Allow custom Slack webhook URLs when integrating with Crashlytics
Problem
When filling out the form to add a Slack webhook URL for a Crashlytics project the form only allows URLs that begin with https://hooks.slack.com/..., however, some companies have their own proxy URLs to manage the Slack webhooks for their enterprise Slack instance (e.g. https://hooks.mycompanydomain.com/...).
Feature request
Please relax the client-side only form validation to allow other hostnames besides "hooks.slack.com".
10 votes -
Support deleting databases via the API
You cannot delete a Firestore database with the API; you must use the CLI if you want to do this programmatically. This is problematic as it means you essentially need to create a shell in your application, ensure the CLI is available, authenticate, and then make the required CLI call.
2 votes -
Support deleting collections in the API
Currently you can only delete collections programmatically via the CLI. Otherwise, you have to list and delete every single document in the collection. If those documents have nested collections, you have to (recursively) retrieve and delete every document in the nested collection (As deleting a document does not delete any nested collections the document has). If there are additional levels of nested collections... You get the idea.
I wasn't sure what this other request was referring to so I made this one: https://firebase.uservoice.com/forums/948424-general/suggestions/46562317-api-support-for-deleting-directories
7 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
-
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 -
Expose "last updated" metadata
If Firebase cannot support some kind of changestream implementation, it should include metadata on each document that includes a "last updated" timestamp. Then clients can query against this field to only retrieve "new" changes (Inserts, Updates). It lacks support for delete capture but is the next best thing after a changestream.
18 votes -
Changestream
Firestore does not support any actual CDC (Change Data Capture). A changestream similar to other NoSQL implementations (Mongo, DocumentDB, Azure Cosmos DB) would make the database a lot more usable and grant feature parity with other popular NoSQL databases. This changestream would expose operations like updates, inserts, and deletes for a client to come and retrieve from either a timestamp or a resume token.
8 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 -
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 -
firestore 'in' 2d array order optional
For some reason an 'in' wury with a 2d array also runs with a sort function. which is not provided or supported by other features such as ArrayUnion and ArrayRemove.
the order should be an optional parameter because using a system where we must find all other documents that have the exact same features but maybe in a different order, is not possible. there is no native sort option when using ArrayUnion, and we've been taught through firestore arrays in general, that orders of items fundamentally shouldn't be considered to exist due to idempotency.
TLDR:
ArrayUnion does not support 'in…1 vote -
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 -
Blocking Functions for User Reset password
Currently you can only add blocking functions for User signup and User sign in. I want to be able to add a Blocking function for User Reset password.
This way I can customize password requirements at the API level and implement features in Cloud functions + Firestore such as preventing previous password reuse.
I would have used Cloud Functions + Firestore for my Blocking function, but because this feature didn't exist I ultimately decided to move my auth password checks to my AWS hosted backend API.
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 -
Auth: install, not only authorise, a GitHub app
GitHub Apps are now the preferred alternative to GitHub Oauth Apps. When authenticating with Firebase Auth and a GitHub App, the app is "authorised" but not "installed", which can lead to inconsistent behaviour (https://github.com/orgs/community/discussions/61677). It would be nice if the GitHub provider had an option for prompting the user to "Authorise and Install" rather than only "Authorise".
2 votes -
DataTable widget generated for use in FlutterFlow
Provide a convenient way to manipulate large amounts of structured data.
For example, using it to display a list of a company's employees, with each row representing an individual employee and the columns showing the employee's name, age, department, and salary.
This list may contain standard CRUD icons and of course Column Placeholder (Set from Variable).
In the end, it is the automation of a CRUD described in the link https://docs.flutterflow.io/widgets-and-components/widgets/base-elements/datatable1 vote -
java admin sdk doesn't have feature to generate a shareable url for a storage file
The feature is already present for nodejs:
https://firebase.google.com/docs/storage/admin/start#shareable_urls
The same should be implemented for Java.
2 votes -
Setting claims to AppCheck token
We use AppCheck for protecting server. But we don't know if this token is shared from other users or not, because the token doesn't have any user identity who issued the token. We would like to set userID to the claims in creating AppCheckToken. And at server, we check userID in the claims.
6 votes -
Support firebaseui-web
This highly valuable library is out of date with many issues.
1 vote -
Allow use of document value as query paramter
Especially a parent value of a subcollection. For example, to be able to read data about a User while querying a subcollection called "Responses".
1 vote
- Don't see your idea?