1220 results found
-
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 -
Firestore : Throw error access data with offline cache without enable persistence
When retrieving documents from Firebase's Firestore on the web, if you attempt to read the value from the cache, it will return an empty result.
This seems to be an issue because Firestore's database does not use offline data when accessed from the web by default.
To make developers aware of this, should throw some error if Firestore's database is set to not use offline data, and attempting to read the cache value.
5 votes -
58 votes
-
Working perfectly fine
Excellent
1 vote -
Allow Trending Stability Notifications via the Slack integration
I would like the option to be able to receive trending stability notifications via the slack integration
19 votes -
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 SMS customization & add Web OTP support
Web OTP support increased phone authorization conversion significantly.
Currently, We are not able to customize SMS messages to comply
https://developer.chrome.com/en/articles/web-otp/#format52 votes -
Have a calendar view for push notifications so I can keep track of what's going out when
Have a calendar view for push notifications so I can keep track of what's going out when
2 votes -
BlackList for Hosting
Please block access from this UserAgent.
"Bytespider; spider-feedback@bytedance.com"4 votes -
Make wonderful gaming apps
Gaming apps is the importance for everyone who are interested on playing games in online
4 votes -
[Email Verification] Need to have a param to set expiration time
As of now, there is no way we can set a custom expiration time for the Email Signin with link authentication. Our use case is that we generate this link through admin sdk and then mail the users (as an invite).
Hence, it becomes really important for us to have a custom expiration time.
3 votes -
Support TypeScript in Cloud Functions
It's a pain to have to configure a process to watch and transpile TypeScript files to use in the emulator. Firebase CLI should have built-in support for it both in the emulator (with automatic watching, or on-the-fly transpilation as I showed here https://github.com/firebase/firebase-tools/issues/5633#issuecomment-1622585432) and when deploying.
34 votes -
Deploy Private HTTP Firebase Functions without "Allow unauthenticated"
By default HTTP Firebase Functions are made public. In Google Console they are marked as "Allow unauthenticated" because they will allow all callers, without checking authentication.
I would like an option to deploy them privately.
Example:
const privateFunction = onRequest(
{
allowUnauthenticated: false,
},
(req, res) => {
res.status(200).send(req.body);
},
);5 votes -
Firebase messaging SDK with proper error response message in emulator
I encountered an issue while attempting to emulate the sending of push notifications with a Firestore Cloud Function. Despite having valid tokens set up, I received an error response. The error messages I received after attempting to send two push notifications individually were as follows:
"Error: Requested entity was not found."
"Error: The registration token is not a valid FCM registration token."Ideally, I would expect to receive a 200 or 403 response along with a message indicating that the message was sent successfully, but that this is only an emulation environment. Upon deploying the latest version of my script…
4 votes -
Full-stack preview channels
Hosting preview channels are great, and work well for client-side code, however for full-stack apps that require a server (either for SSR or API routes), the preview channel uses to the 'main' server as a backend. It would be great if the server side code also got deployed to a new firebase function and was managed alongside the hosting preview.
5 votes -
55 votes
-
It is necessary to change and update in advance the spread of better ideas that benefit people and reduce harmful materials
It is necessary to change and update in advance the spread of better ideas that benefit people and reduce harmful materials
2 votes -
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 -
Add an argument that automatically chunks cloud function deployments according to the maximal possible quota
When deploying multiple cloud functions at once via
firebase deploy --only functionswe frequently run into quota issues like:
functions: got "Quota Exceeded" error while trying to update projects/.... Waiting to retry...
It never retries though.
It would make it way easier if you could add an argument to the deployment command like:
firebase deploy --only functions --chunked 504 votes
- Don't see your idea?