1222 results found
-
Similar to __name__, allow ordering documents by internal createdAt / updatedAt sentinel value
A document always maintain createdAt / updatedAt timestamp value internally. But these fields can't be used for ordering documents.
For example :-
(This is possible)
await citiesRef.orderBy('name').limit(3).get();
(This is NOT possible)
await citiesRef.orderBy('created_at').limit(3).get();
Currently if we need order by timestamp, we need to maintain a separate timestamp field alongside internal createdAt / updatedAt fields. Then create index over that additional field to perform order by timestamp.
Similar to name sentinel, firestore should provide created_at and updated_at sentinel for ordering document. These sentinel should work without any new index, ascending or descending order.
1 vote -
IOS SDK should have initializer simple initializers
Right now the SDK generated only has init with decoder.
public init(from decoder: any Decoder)
This limits us in generating the Previews for the views. Please consider adding additional inits with all variables in the struct
1 vote -
Add Linux platform support
What feature would you like to see?
I would like to see Firebase add official support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services natively on Linux, enabling broader platform compatibility and empowering Linux-based applications.Why would it be useful?
Adding Linux support would:Enable developers to integrate Firebase services directly into Linux-based applications.
Provide parity with other supported platforms (e.g., iOS, Android, Web).
Open up Firebase's powerful features (e.g., authentication, cloud storage, Firestore) to a growing user base on Linux desktop and server environments.2 votes -
1 vote
-
Support backend modification or deletion options
Currently, we can create backends, but there is no option to modify imported GitHub repositories. If making such modifications isn't possible, it would be beneficial to at least have the option to delete the backend.
1 vote -
Support UUID as a data type
I'm using Go client, and at this time UUIDs are represented as array of numbers. This doesn't make any sense and is quite clunky and unergonomic, but this is the client behaviour - the Go type
[16]byteconverts to that, and there is no way to affect it directly.This also means that a list of UUIDs is impossible to represent at all, since a Go slice converts into an array, and Firestore can't handle arrays in arrays. Btw, that by itself is ridiculous, but right now my problem is with UUIDs specifically.
A list of IDs is a trivial…
1 vote -
Allow cross-project restoring of Firestore databases
When working with Firestore databases, you may want to restore an entire database for testing in your stage project.
However, currently, you can only restore in the same project
1 vote -
Unique password option for password policy
Add an option for the password policy to require users to create a new, unique password that has never been used for their accounts.
1 vote -
Working perfectly fine
Excellent
1 vote -
rules map
In Firebase Firestore rules, we currently have various controls and functions, which are very handy. However, array management is not optimal. I propose introducing a map function for arrays in Firebase Firestore rules. This function would allow us to map arrays of objects, significantly simplifying the creation and management of rules.
1 vote -
Allow to assign tags to Firestore databases
With multi-db support in Firestore now launched, this enabled many possibilities but also requires more granular inventory management of the databases created.
--
For compliance reasons and for better management of your cloud assets, it's important to assign metadata to your cloud resources.
Especially for storage services, this is important, as it allows you to track which resources contain PII, who owns them, etc.--
Attaching this kind of data is typically done using tags in Google Cloud.
If it would be possible to attach tags to individual Firestore databases, this would solve the management of databases and allow easier…1 vote -
Allow to attach IAM permissions to databases
With multi-db support in Firestore now launched, this enabled a ton of new features, though the way permissions are granted is not ideal.
--
Instead of being able to attach permissions to individual databases, you have to use conditional IAM permissions on a project level.
--
This leads to problems when you want to grant IAM permissions to employees with access to only a subset of databases.
Granting a subset of databases to access will prevent them from using the Firebase / Google Cloud console, as they will not have permission to view all databases.--
Also conditional IAM permissions…
1 vote -
native
nativePollOnce should be excluded from ANR in Firebase
1 vote -
Allow use of the filter value on whereArrayContains within a firestore rule
I believe that by simply allowing access to the whereArrayContains filter value, it should be possible to solve for a use-case which can generally only be resolved using an SQL/relational database or cloud functions.
Take the following query;
getDocs( query( collection(db, "profiles"), where("groupProfileLinkIdReference", "array-contains", "groupProfileLinkId1"), limit(1), ), )If we can access the value which in this case is "groupProfileLinkId1", it becomes possible to do the following;
match /profiles/{profileId} { allow list: if validateListProfileDbEntry(); } function validateListProfileDbEntry(){ let groupProfileLinkId = resource.data.groupProfileLinkIdReference[0]; let groupProfileLink = get(/databases/$(database)/documents/groupProfileLink/$(groupProfileLinkId)).data; return groupProfileLink.isApproved == true; }The way the data is modelled is that every time…
1 vote -
5 emails
I saw this on the documentation website: "Note: The limits for email link sign-in emails were recently changed. Please add a billing instrument to go beyond 5 email link sign-in emails."
It's really strange that you quietly set the limit of sign-in emails to 5. Why? It makes no sense. For testing it's too low, and for production of course.
First you hook developers up to Firebase and then you quietly lower the limits. Good business practices.
1 vote -
free
please support me
1 vote -
Orderby('any_potential_null_field', excludeNull: false) should exist
OrderBy should be able to return collection item when target property is null.
1 vote -
Page not found
I created a deeplink that opens in the in-app browser.
Sometimes this deeplink works correctly for some users, while for others it does not. When it doesn't work, users are redirected to a Firebase error page (Page Not Found).I tried encoding the URL used as the Dynamic Link,
but it still sometimes results in a Page Not Found error.The main issue is that the same Dynamic Link URL works for some users but not for others.
What could be the cause of this?1 vote -
support .guru domain extension
I have a domain with the extension: .guru,
but when I enter the domain to firebase for authentication, it doesn;t accept it as a valid domain name! HELP PLEASE!1 vote -
1 vote
- Don't see your idea?