136 results found
-
1 vote
-
Improve firestore rules debug info
Improve firestore rules debug info:
2 features will really improve the debugging of firestore rules:
- Add a "label" parameter to the debug() function to identify the result in the debug log file of the emulator. Right now, only the value is printed, it is very confusing when you have several debug calls...
- Improve the error message returned to the client so we can understand the permission denied. Right now the message contains very little information and it is not helpful a all..,2 votes -
1 vote
-
Put the collection name in the beginning of the page title of the Firebase web console
Right now it goes "Project Name - Database - Data - Firebase console" which can get confusing when i have multiple tabs open.
2 votes -
[HIGH] Add support for bitwise operators in security rules
It would be nice if we have support for & | ^ bitwise operators in security rules for both firestore and cloud storage.
This highly improves roles and access rights check using only one integer instead of a Map of booleans.1 vote -
Add copy source code to Firestore Query Builder
It'd be great if Query Builder had a way to translate whatever query you're running into a code snippet. Something like Firestore's docs where you can select a language and then copy the code.
1 vote -
1 vote
-
Firestore Rules Tab - Separation of Concerns
Firestore rules tab should allow deploying multiple tabs so that all rules are not in the same rules container in the UI. This will allow us to create separation of concerns(collections) to their own tabs. To prevent massive running list of rules.
As an example:
I have 2 collections
Users
PetsI should be able to write my rules for Users in a tab.
Then in a completely separate tab, write the rules for PetsThen deploy them individually or all at the same time.
4 votes -
to
Rofikul22114
1 vote -
🔥🗑️ Desaster recovery for full firebase project
It would be great to have a daily disaster recovery feature for the entire Firebase project, not just Firestore. Rollouts can corrupt auth objects or storage files (e.g. user images), and while Storage backups can be automate (e.g. via Transfer Service), there's no built-in way to automatically back up and restore Firebase Auth. Ideally, there would be a "Timeline" tab in the console, allowing you to rollback the full project—Auth, Firestore, Storage, or any other service used —to any recent daily snapshot, with of course costs depending on read/write/storage usage. This would significantly improve safety and confidence during production changes.…
7 votes -
Allow to convert a Set() to a List() in the Firestore rules
There is a very annoying limitation in the Firestore rules: you cannot convert a Set() to a List().
This prevents a lot of possibility especially when using Map().diff().affectedKeys(): there is no way to access the first element for example.
My use case is the following:
On my client side, I am incrementing the value of a map element, ie:
MapFieldValue resources;
resources["gold"] = FieldValue::Increment(-amount);And on the rules side, I want to ensure that the resulting value is always positive (ie you cannot spend more gold than you have, even concurrently!):
let updatedKeys = (resource.data.diff(request.resource.data).affectedKeys());
return (updatedKeys.size() == 1 &&…1 vote -
firestore pipeline as rulev3/transformation
Additional to just a condition for allow read/write. I think firestore rule should be replaced with transform function. It should utilize pipeline operation and return document to read/write. So that it could force add field or change logic to generate some field on every document without redeploy client
1 vote -
Query filter for Nested Arrays
Adding a query method to filter the nested arrays in the firestore collection would be more scalable to get data faster. This would avoid the unnecessary looping of the data for finding a particular field, which are already stored in an array.
This feature would make the firestore to perform extraordinarily in retreiving the data.
2 votes -
Allow String to Timestamp conversion in Firestore rules
In Firestore rule, it could be very powerful to convert String containing date to Timestamp. For example, the RevenueCat extension store date as ISO 8601 string and we can't use them in firestore rule because date are not Timestamp.
In my Firestore rule, I would like to do something like :
timestamp.parse(collection.data.expires_date) > request.time
27 votes -
มองทาง
ดูเเล้วลงมือทำในสิ่งที่ดูเพื่อเพิ่มศักยภาพในการทำงานของระบบปฏิบัติอยู่ที่ตรงหน้าเท่านั้น
1 vote -
Enjoying the clean, simple design for Real-time Database
Just positive feedback for the Firebase team! I'm a retired software engineer developing small 2-D Android-based games for my family and others.
The real-time database allows me to run these games across the web, among mukltiple Android devices, with no need for a "back-end", and is so much cleaner and easier to set up and use than the Android Bluetooth APIs, which are of course limited in scope and reach.
THANK YOU to the Firebase team for providing such an elegant service.1 vote -
reference Bazel label paths for dependencies, possibly from a BUILD file or workspace definition.
UUID Group Name
74fd13fa90f483537a1866505fae79762f121b96 Empty Group = NoOne
c70777b3b2b15fd1baf444b2b6e968d75e3a405c chromeos-committers
global:Anonymous-Users Anonymous Users
global:Registered-Users Registered Users1 vote -
4 votes
-
4 votes
-
Bd
Xvkxc
1 vote
- Don't see your idea?