2216 results found
-
4 votes
-
Remote Config fetch data from only selected groups
Current data fetch is not filtered at query level and all of your config fetches to your frontend. This means for example, IOS app fetches IOS, Android and Web config if all apps fall under the same project.
4 votes -
Support Bitbucket
Support bitbucket as a source repo provider
7 votes -
Add GitLab as a Provider to be able to link repositories
Ask the cloud team to add GitLab as a Provider, including the CE version.
7 votes -
poetry
Poetry is the true path of life and available for people.
1 vote -
Devcontainer Support
Some of us come from Codespaces and other IDEs who already invested in Devcontainers. It would be nice if that's supported OOB
2 votes -
Support for Remix
Add Remix (https://remix.run) as one of the supported frameworks to deploy apps. It is rather similar to Next.js in many ways so that should be possible.
5 votes -
78 votes
-
Search collections in Firestore by field values
Ability to search collections and documents in the Firestore UI.
87 votes -
Uprade to latest code-oss
Current version of 1.89.1 was last updated in June in IDX, and running into issues with some of the newer/updated VSIX extensions.
1 vote -
I suggest that Project IDX provides the IP addresses for its domain, so users can whitelist these in the variuos AWS, GCP, cloudSQL setups
I suggest that Project IDX provides the IP addresses for its domain, so users can whitelist these in the variuos AWS, GCP, cloudSQL setups
3 votes -
Add functionality to increase sampling rate
It would be awesome if we can see more sessions data in firebase as compared to how many samples are been generated. The current sessions data is generated at the rate off 1%, and if we can manipulate the same, it will be great
4 votes -
Add support for Deno
Deno is a pretty solid modern JavaScript runtime that's been making a lot of great progress lately.
5 votes -
API Project Support
If you are building a backend API, we would like Project IDX to support creating them across popular endpoints. We would also like to explore integration with services like Postman to make testing these endpoints easier.
63 votesWe are actively working on addressing these items. Stay tuned for some updates here.
-
request.query security rules
currently security rules can only check, "limit, orderby and offset" properties of "request.query" object. if they could check our own custom properties , for example, when users search a collection by id, and I only want them to see a list of documents which contain their id then i should be able to do this in the rules
posts/{postId} {
list: if request.query.id == request.auth.uid
}
- this would be really beautiful and makes it way easy to secure list request.3 votes -
Support adaptive app icons
Android 8.0 (API level 26) introduced adaptive app icons, which are made out of background and foreground layer. Apps that have minSDK = 26 don't have to specify "flat" PNG icons. However, App Distribution doesn't support adaptive app icons, and as a result weird icon with cropped app name is displayed in the App Tester app. App Distribution should support adaptive app icons by parsing icon XML, obtaining foreground and background assets, and based on this render the icon.
12 votes -
7 votes
-
We've detected suspicious activity on one of your workspaces. Please contact support for further assistance
would be nice if this thing tells what type of suspicious activity was detected and have actual options to fix it. or maybe even warnings so that people don't work too ******* something just for google to restrict access out of nowhere.
1 vote -
Android studio on wait list!!
I am using Android Studio daily basis. right now, it shows Android Studio on the waitlist. Hope it is done very soon and available for all.
4 votes -
Similar to __name__, allow ordering documents by internal createdAt / updatedAt sentinel value
A document always maintain createdAt / updatedAt timestamp value internally. But these fields can't be used for ordering documents.
For example :-
(This is possible)
await citiesRef.orderBy('name').limit(3).get();
(This is NOT possible)
await citiesRef.orderBy('created_at').limit(3).get();
Currently if we need order by timestamp, we need to maintain a separate timestamp field alongside internal createdAt / updatedAt fields. Then create index over that additional field to perform order by timestamp.
Similar to name sentinel, firestore should provide created_at and updated_at sentinel for ordering document. These sentinel should work without any new index, ascending or descending order.
1 vote
- Don't see your idea?