695 results found
-
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.1 vote -
linux
What feature would you like to see?
I would like to see FlutterFire plugins add support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services on Linux, enabling cross-platform compatibility and expanding Flutter's reach.Why would it be useful?
Adding Linux support would:Enable developers to target a wider range of platforms with their Flutter apps.
Provide parity with other supported platforms (e.g., iOS, Android, Web).
Leverage Firebase's capabilities (e.g., authentication, cloud storage, and Firestore) in desktop environments where Linux is widely used.1 vote -
Documenting Schema and Connections
One of the things that was important to me when developing clients in Apollo graphql is the playground.
You should be able to create a document with a proper description.
And currently, description using “”” is only possible for schema type. It is also needed for query, mutation.
And we need to be able to generate them with the SDK and then see them in the client code.3 votes -
Allow secrets on scheduled functions
It's not clear in the documentation nor by implementation that secrets work with scheduled cloud functions. This seems to me like a major missing feature in security and consistency with the v2 cloud functions. Is the only solution using the cloud config for api keys/secrets?
We need to have something like:
exports.someScheduledFunction = onSchedule(
{
schedule: "every 60 minutes",
timeoutSeconds: 100,
secrets: [someToken.name],
},
async () => {
logInfo("Running every 60 min");...
}
);1 vote -
allow secrets on scheduled functions
It's not clear in the documentation nor by implementation that secrets work with scheduled cloud functions. This seems to me like a major missing feature in security and consistency with the v2 cloud functions. Is the only solution using the cloud config for api keys/secrets? Something like:
exports.someScheduledFunction = onSchedule(
{
schedule: "every 60 minutes",
timeoutSeconds: 100,
secrets: [someToken.name],
},
async () => {
logInfo("Running every 60 min");...
}
);1 vote -
Analytics Admin Sdk
Create Api for Firebase Admin SDK to get analytics data.
1 vote -
1 vote
-
Geohashing examples for firestore Python Admin SDK
I have read this article https://firebase.google.com/docs/firestore/solutions/geoqueries in mentions cool examples on how to implement Geohashes, but I can't find python examples. Is there a recommended way of implementing geohashes on Firebase Admin SDK for python?
1 vote -
Firebase-UI Support
The firebase-ui https://github.com/firebase/firebaseui-web seems to no longer be supported. It currently doesn't support the latest firebase versions: https://github.com/firebase/firebaseui-web/issues/1107
17 votes -
Fix Body Parse
If bad JSON is sent to a cloud function, for example if the function is an API endpoint, the body-parse in Firebase Functions will throw an HTML response error before and user function code is run.
This is a really bad experience for endpoint users where instead of a formatted JSON error message, they get a strange HTML response.
The body-parser used in by Firebase Functions should pass along the error instead of returning the response.
2 votes -
App Distribution API includes information whether tester have installed the app
Currently the only way to know whether a tester have installed a version is through the Firebase Console. I wish we could get this information through the App Distribution API too. Currently we only have lastActivityTime which is not very useful: https://firebase.google.com/docs/reference/app-distribution/rest/v1/projects.testers#Tester
2 votes -
Support Public distribution group to allow user to install app on their device without authentication
However, Firebase lacks the feature to share debug builds with a public distribution group, like Microsoft AppCenter offers, without adding testers. Sharing public link users should be able to install on their devices without authentication.
9 votes -
Add service to Data Connect Triggers
Trigger a Cloud Function that will add the service and schema to Data Connect when the user signs up successfully.
2 votes -
notes
Add Crashlytics Issue Notes to the Crashlytics Schema [1] for BigQuery Export [2]
[1] https://firebase.google.com/docs/crashlytics/bigquery-export#schema-columns
[2] https://firebase.google.com/docs/crashlytics/bigquery-export2 votes -
Add GraphQL enum support
Add support for the GraphQL enum type in @table types.
19 votes -
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 -
Console: free up space to work on medium size screens
Outside the office, I work on an 11" Chromebook and the console layout is not at all user-friendly for screens that are not large.
The spaces in the appbarr, title, navigation and footer bars take up a lot of space and are fixed, the content of the page that is left for editing is very limited, having to scroll each line and some services do not even have space to open the item to be consulted, like in analytics, for example, some cards are truncated.1 vote -
Enable keyboard navigation in Firestore console to move between documents using up/down arrow keys.
I suggest that Firebase enhances the Firestore console by adding support for keyboard navigation, allowing users to move between documents using the up and down arrow keys. This feature would improve accessibility and efficiency, especially for users who prefer using the keyboard over the mouse or trackpad. Implementing this functionality would make data management in Firestore more user-friendly and accessible to a wider range of users.
1 vote -
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 -
Provide an option to only deploy new parameters
Consider the scenario where you create a new Remote Config parameter in your template.json file and deploy it via the Firebase CLI to TEST and PROD environments with a default value. You then modify the value in PROD via the Firebase console. The next time you deploy Remote Config to PROD the value is overwritten. It would be useful for CI/CD deployments to have an option that would only deploy new parameters and would NOT overwrite the values for existing parameters. This would allow you to structure your template.json file to have default values for new non-PROD environments without having…
1 vote
- Don't see your idea?