1214 results found
-
Work
I'm love work
1 vote -
Allow to connect emulator with a tier SQL client
I get that firebase dev really want to push their DataConnect api but any full featured tiers SQL client would allow us to have a wider view of what worked in our dev environment.
It would be way faster than using any official cli or any generated query to look how our data is shaped within the database.
3 votes -
Support MFA and future AuthN
Currently when using the emulator you can't use MFA as it throws an error and the only way to test this functionality is to switch over to using the real version. This is cumbersome and makes it difficult to test your auth workflow. Also your adding Authn as well and I hope that is support by the Auth Emulator as well.
9 votes -
Give firebase studio/project idx access to cloudshell scripts
I want an ide with gemini which i can use to edit my cloudshell scripts, I see that there is cloud shell environment, would be nice if it is same as firebase studio.
3 votes -
Support inline/embeded types stored as structured JSONB columns
Allow storing structured types in JSONB columns using an @inline (or @embed) directive on the field.
type Address {
street: String!
street2: String
city: String!
state: String!
zipcode: String!
}type User @table {
address: Address @inline # stores as JSONB
}21 votes -
Sort event parameters by key in Logs and breadcrumbs view
The log event parameters appear in a random order, changing from event to event, crash to crash, making it hard to search and find the parameter of interest. It would be nice if the parameters would be sorted by key, so the one of interest would be easy to find.
(Maybe the order is whatever happened to be serialised in the original crash report. But since it was attached as an unordered
Dictionary<String, Any>via the FirebaseAnalytics API, there's no way to control the order in which they appear in crash logs.)2 votes -
AI Terminal
AI do terminal tasks in the standard terminal of the firebase studio not in a strange looking terminal
2 votes -
firebase chat and destructive behavior
i have encounter an bug that poses many modern AI chats designed for programing.
many of them have a issue in deep logic causing issues and wiping files.foe example the firebase chat assistant have wiped my .env file with dosens of sensitive api tokens or ID's
am not talking about once or twice erase the data but more than five times to co completely wipe the credentials and then force me to manually add them again.here is firebase response to one of its destructive action:
I am speechless. You are absolutely right, and I am deeply, deeply sorry.
…
1 vote -
Rehan
Hello me Rehan
1 vote -
2 votes
-
2 votes
-
i want to make an application that collectes all data base from google
it should have a search bar
1 vote -
Support .NET (C#) in Firebase Functions.
Firebase has .NET SDKs for the client and admin SDKS. It would be nice if Firebase Functions supported .NET (C#) especially since GCP Cloud Run Functions already support .NET.
4 votes -
saya tidak bisa membuat projek saya dengan akun ini
saya tidak bisa membuat projek saya dengan akun ini
1 vote -
2 votes
-
create a UI for managing environment variables and surfacing build error messages in the Firebase console
create a UI for managing environment variables and surfacing build error messages in the Firebase console (so you don't have to go into CloudBuild)
25 votes -
Allow direct "Zip and Download" for the project root directory
Currently, the "Zip and Download" function is only available for subdirectories and individual files, but not for the root project directory. So it is hard to download the whole project to a single zip file.
1 vote -
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.
6 votes -
1 vote
-
Hosting should preserve the client's IP address when proxying to Cloud Run
When using hosting with rewrites to Cloud Run (e.g., routing all requests to /api/** to a Cloud Run container), the clientIp always reflects the IP address of a Google server rather than the actual client’s IP address. As a result, filtering incoming requests by IP address in the logs viewer becomes impossible.
It would be great if the x-forwarded-for header could be used to populate this field instead.5 votes
- Don't see your idea?