1236 results found
-
Allow specifying number of stored releases when creating a preview channel
Preview channels by default store 10 previous releases per channel. When running firebase hosting:channel:create there is the --expires option to set when the channel expires, but there is no option to tell firebase how many previous releases to store.
In my case I don't need previous releases at all, and the extra storage is completely unneeded and makes us hit the quota earlier.
3 votes -
Design an app that uses the phones full potential
To help the homeless is my reason cause I am currently homeless so the news is great also it has a Robin Hood theme cause we are gonna use the money from the people that are lying and down if to the ones the actually need it .... Using facial recognition and heart beat and want eher else the phone is capable of
3 votes -
I would like this to be a team effort
My idea is that the collective will come together and use that to our advantage anything to make this become a reality
2 votes -
i cant create the Storage shows An unknown error occurred.
i cant create the Storage shows An unknown error occurred.
2 votes -
Custom Serverless Resolvers
Write Node.js resolvers to enhance Data Connect with arbitrary server logic. Resolvers will be authored alongside the Data Connect schema and deployed to serverless infrastructure. Resolvers can either provide new top-level Query and Mutation fields or integrate with SQL table types.
39 votes -
Improving generate idea loader experience
The loader that is shown while waiting for the AI to work on your idea should be progress indicator instead of some animated loader that just animates. This is not properly telling me if there is an issue or is the app is being created. I am just waiting to see the results
2 votes -
Allow For Different Rollout Percentages
Currently, the highest allowed rollout percentage is 50% (before going to 100%). While we understand that higher percentage won't allow to compare the groups correctly, having an ability to gradually release a feature from 50% to 100% would be a very nice and common requirement.
6 votes -
Obfuscate or hide GoogleService-Info.plist
Secret information in GoogleService-Info.plist is easily accessible by downloading .ipa from App Store via Apple Configurator and unpacking it. That is a big security issue.
1 vote -
1 vote
-
@Model Operations support in Schema (@auth derivative)
Right now we have separate Query and Mutation. To streamline, especially when using @auth
enum ModelOperation {
create
update
delete
read
}@auth object types that are annotated with @auth are protected by a set of authorization rules that give additional controls than the top level authorization on an API.
Use the @auth directive on object type definitions and field definitions in the project's schema.
When using the @auth directive on object type definitions that are also annotated with @model, all resolvers that return objects of that type would be protected. When using the @auth directive on a field definition,…
2 votes -
Fix error messages when deploying Functions
Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:
i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.
I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.
The second time, it got further, but…
4 votes -
Transaction should update the local offline cache
It is a surprise to users (and Gemini) that writing documents using a transaction does not result in the local offline cache being updated when the transaction completes successfully. I'm not sure that it makes sense for the SDK to do this automatically but the firestore docs need to be updated (including the code examples) to make it clear that the local cache does not get updated. There may be some documents in the set being written that are never written by other users, in which case the local user is not expecting to have to have a listener running…
2 votes -
Creating a project directly into the Server or Hosting would be great.
When users who accept security risks give their hosting information directly... artificial intelligence should be able to create files and databases within this host and create a project with the desired features in natural language...
2 votes -
Icp Cube
NLB.com Jrr.com
2 votes -
PROPULSION VIA Q compute
continue DoD WORK VIA Q compute©
3 votes -
datos de contacto para mi aplicacion
necesito que mi aplicacion recolecte los datos del consultante Nombre, Whatsapp con codigo de pais + email de contacto
2 votes -
Add support for local npm packages
Change the behavior of dpeloy for functions so that if a local (file based) npm package is listed in the package dependencies, the package will be uploaded with the function.
It is a major pain for local packages to not be supported in uploading cloud functions.
6 votes -
"chat mode" like in lovable
a chat mode to discuss prompts or functionality or development ideas
3 votes -
Support Swift in Cloud Functions
Swift is a much beloved and popular language for writing apps on the Apple platforms, but increasingly, it is also being used server side and even for writing cross platform business logic on Android and on Windows.
Being able to share models and business logic between your clients and server would be an amazing productivity boost. And being able to develop in a language that focuses on safety would eliminate categories of issues that can exist if you develop in say Javascript or Typescript.
345 votes -
Sending arrays as parameters, to allow scaling.
When building simple select queries in GraphQL (really simple ones), the underlying query is being transformed, sending the values through as parameters.
As you can use arrays as parameters, that would allow the DBs to scale as it makes this more robust. Without scaling, it will limit production applications form fully investing.
As an example you run into instances where the select for 50 columns in the schema (a standard employment record, nothing special) is transformed and we end up getting the dreaded 100 parameters error. This is a Postgres issue, but can be avoided.
The Error for the fun…
5 votes
- Don't see your idea?