728 results found
-
API support for insertMany and updateMany
Currently Data Connect insertMany and updateMany mutations do not support being passed multiple records via the SDK. Figure out a way to enable this so we can insert multiple rows in the same “@transaction” via the API.
1 vote -
@unique argument to use UNIQUE NULLS NOT DISTINCT
Add an argument to the @unique annotation that allows users to choose between using PostgreSQL's "UNIQUE NULLS NOT DISTINCT" constraint or the standard "UNIQUE" constraint when defining a unique constraint.
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 -
Vector embedding search should include distance in results
The newly released capability is https://firebase.google.com/docs/firestore/vector-search is working very nicely! However, all similar products should return the distance metric in the query results (which the backend has no doubt already calculated) so that the client perform further analysis based on that distance
8 votes -
Clickable results in firebase query mode
When using Firebase UI query mode, the results are not really human readable. I'd like the document ID field to be clickable, taking me to the panel view of that document, so I can see the document in a readable way.
1 vote -
Enhanced Foreign Key Behavior
I am reaching out to share a suggestion regarding the current implementation of foreign key constraints in Firebase DataConnect.
Currently, it appears that the default behavior for foreign keys is automatically assigned during schema deployment, and there is no way to explicitly define ON DELETE and ON UPDATE rules (e.g., NO ACTION, CASCADE) in the GraphQL schema. This limitation has the following implications:
1. Deployment Overrides: Even if these rules are manually adjusted in the underlying PostgreSQL database, deploying an updated schema resets the rules to the platform’s defaults.
2. Lack of Customization in Schema: Adding support for directives like…2 votes -
Add IS_NOT_NULL (x.where("field", "!=", None)) operator to filters
This allows filters like x.where("field", "!=", None) to work, matching the JavaScript implementation and Firestore GUI implementation. The feature is late by 4 years.
https://github.com/googleapis/python-firestore/pull/971
https://github.com/googleapis/python-firestore/issues/9702 votes -
117 votes
-
Firebase project config in env
Cloud functions do provide process. env.FIREBASE_CONFIG.
One can set it in the yaml, but it would be nice if app hosting would provide these automatically.
1 vote -
Allow rewrite for hostname/domain (not only paths)
It would be great to have the ability to redirect multiple domains to the same project.
I tried to achieve this with regular expression redirect, but it doesn't work:
{ "regex": "https:\\/\\/.*?(?P<hostname>\\w+\\.[a-z]+)\\/", "destination": "/:hostname/index.html" }For example with domains one.com and two.com, I want to be able to redirect them to the same project but different subfolders (e.g. /one.com/index.html, /two.com/index.html) -- this will allow to share common resources (styles, images, etc) between the projects, while still being able to customize the content for each one.
1 vote -
Firebase Admin Lite
Right now you can't host Firebase on Cloudflare, Vercel Edge Functions, Bun, or Deno without using the "Firestore Lite" package. However, there are no "auth" functions, and no access to admin functions. We will need to create server sessions etc on the server. This cannot be done in NON NodeJS environments without the REST API. There needs to be a Firebase Admin Lite package, or the very least add an "auth" lite package.
8 votes -
Support submodules
Support submodules for automated builds.
Currently, builds fail when checking out submodules.
1 vote -
Authentication using email OTP verification for Firebase login
I want to be able to perform an OTP verification for logging into my application using firebase.
I want this feature to follow the following user journey:
- Request OTP for login.
- OTP sent to my email.
- I type in the OTP for verification.
- Authentication and access granted.1 vote -
Add a disable-billing button in addition to the budget alert option
Add a disable-billing button in addition to the budget alert option. This should be a user-friendly option: https://www.youtube.com/watch?v=Dk3VvRSrQIY&list=PLl-K7zZEsYLmK1tiMBeKA0iDMPDCJKM-5&index=7
2 votes -
Better Composite Indexes UI
Currently, table for Composite Indexes is hard to read, I have some suggestions:
1. Sort collection ID alphabetically
2. Group by collection ID
3. On Fields Indexed, remove "name"
4. Shorten "Ascending" to "Asc" and "Descending" to "Desc"
5. Fields shown in Fields Indexed column should be displayed vertically1 vote -
Support a repl/shell in firebase CLI
Some operations can only be preformed through the firebase-admin SDK, or sometimes you just want to run/test some Firestore query.
The Firebase CLI can provide a "shell" command that opens a Node.js REPL with the firebase-admin SDK preconfigured and global variables such as "db", "auth" that you can then use to interact with Firebase.
This was so much needed that I implemented this by myself in our project as a custom package.json scripts.
1 vote -
Support skipping deploy targets that are configured empty
Sometimes you have deploy target that you want to not deploy in some projects.
Currently if a deploy target is not configured or empty, the CLI will error.
It would be nice if it just skipped deploying that configuration if the deploy target is explicitly configured empty.
This is also useful to allow varying configuration in different projects, as you can deploy different target configurations depending on the selected project this way.
1 vote -
Hosting should preserve the client's IP address when proxying to Cloud Run
When using hosting with rewrites to Cloud Run (e.g., routing all requests to /api/** to a Cloud Run container), the clientIp always reflects the IP address of a Google server rather than the actual client’s IP address. As a result, filtering incoming requests by IP address in the logs viewer becomes impossible.
It would be great if the x-forwarded-for header could be used to populate this field instead.1 vote -
114 votes
-
Custom GraphQL Scalar Support
On top of common scalars such as Email, Phone, etc., custom scalars are defined by developers on the client-side application, with logic for marshaling and unmarshalling the data provided, which could be either a class with the two methods or a couple of functions.
6 votes
- Don't see your idea?