Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

404 results found

  1. It'd be really nice if you could allow users to create local drafts, of small documents, for instance, and save them locally for free with Firestore.

    This way you wouldn't have to coordinate Firestore and its rules with some other database and client code nor would you have to choose the simpler option of getting charged for writes and reads on remote database documents that really only one user is supposed to write and read.

    Please note that while you could use the realtime database to save drafts, 1 it's not always easy to figure out whether that'd actually be…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We sometimes want to target all countries or languages apart from a select few with things we are delivering through remote config. Currently to do this we have to select all other countries and languages and then make sure the one we don't want to serve to is unticked.

    Instead it would be much easier to just target the language we don't want to send it to.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firebase console  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. There should be an easy way to get a specific document by index in a query:

    // this query should work as it's read, if i wanted to use gte i'd use a where

    query(this.collection, orderBy('anything', 'asc'), startAt(index), limit(1))

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Now that we can create named databases and see those databases in the firestore emulator, it would be nice if the import and export-on-exit flags also respected these named databases and imported the data previously exported into the correct database.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Emulators  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The email template should use the Firebase project name instead of the technical code.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Emulators are meant for rapid testing.

    There should be a tool that enables easy fine/grain control for importing and exporting data from the Firebase UI for Firestore, Storage, and Auth from the user interface.

    Trying to manually modify data in the interface is fairly awful.

    It would be nice to be able to mix and match different pre-made documents or collections to set up different types of environments.

    The command line import/export is ok, but still fairly tedious and limiting in its setup.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Emulators  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow deployment from CLI of specific extensions, to avoid uploading and updating all extensions unnecessarily.

    i.e. firebase deploy --only extensions:<name of extension>

    Just like we can with functions.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firebase CLI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. I just spent a week implementing a plugin before realizing it was using Node 12. Deleted all my extensions after that, all using Node 16.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Crashlytics SDK provide support for in iOS app extensions. including the extensions that run in background. For example Location Push Service Extension.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Crashlytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. In this code await admin.auth().createUser({
    email: email,
    displayName: name,
    uid: uid,
    emailVerified: false,
    password: password,
    disabled: false,
    });, if email and password are created, please create the user via that login method and if only phone is provided and no email, then let the user be created via phone auth. So that later on, when they try to sign in via phone auth, the system doesn't create a whole new user with a new uid but just lets the user sign into that account

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Extensions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. I want to ask documentation on how to reduce the number of unnecessary reads. eg. my product data

    let query = store.collection("products");

    Assuming I have 500 products, one user click on get products = 500 reads ? If 100 users click that function, then all my quota is gone in 1 minute. Is that right?

    How can I overcome this.

    Please provide a full example. I have seen Mr Duckworth's presentation in a firebase event, but could not see a good example.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Squarespace has a featured for "site-wide password protection" which is useful for staging unlaunched websites for stakeholders to review. This would help guard against any potential leaks.

    Figma also has a feature similar to this.

    We currently have to create a custom express.js server with an authentication middleware, but this is undesirable for several reasons:

    • We'd have to re-create all of firebase hosting's serving features (i18n fallbacks, redirects, pretty urls, etc.)
    • We can't easily test endpoints that are proxied to Functions/GCR
    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?