1808 results found
-
Feature like RELATE statements
A RELATE statement to adds graph edges between records. Like the convention of vertex -> edge -> vertex or noun -> verb -> noun, enabling the addition of metadata to the edge record.
7 votes -
vim mode
Vim mode is essential for me and I wasn't able to find it as an option. If it is present, could it be made more discoverable? If not present, please add!
4 votes -
Email link authentication API should provide an option to configure the language of the email sent.
Currently, we can just configure one language for every user on the authentication template page. It seems to be possible using "custom email action handlers" but this requires an additional work that is not mentioned in the doc. This lack of option and the additional work to have a usable product in a professional context should be mentioned in the Email Link Authentication doc.
1 vote -
8 votes
-
6 votes
-
7 votes
-
8 votes
-
3 votes
-
Blank template needs to be a lot more... blank
I was really surprised how much content is included in the blank template. I can get behind having the html file, JS, and CSS, but they should actually be empty, or mostly empty. The HTML file can have a base skeleton (html, head, body, that's it), but the JS and CSS files should be empty. I'm having to remove a lot to get to a 'proper' blank.
3 votes -
Jira Cloud Integration for Post production issue type:
Currently, Crashlytics only supports Bug issue type with Jira Integration. It would be helpful if it allowed other issue types, such as post-production issues.
This solution allows users to integrate with their organization's Jira issue-type standards, including Pre-production, Post-production, and Defects, instead of relying solely on the issuetype "bug".
1 vote -
Easy way to start a new project
Once you get into a project, there's no clear way to start a new one from scratch.
3 votes -
Larger more User Friendly Base Text Setting
My suggestion is a larger base text size that is more friendly to the broader public. The IDX base text setting appears to be scaled down. Although this can be adjusted, my initial entry into the application was less pleasant due to how small the text was compared to my usual Visual Studio Code dev environment.
3 votes -
Firestore UI in Firebase Console - Weird bugs
Some issues with Firestore data in the console:
I've noticed that when loading some records in Firestore, the UI will often load for an unusually long period of time (seems like it just hangs), and then as soon as I scroll the window the loading state goes away and the data is shown.
Not sure if that's a bug or something, but it's annoying.
Additionally, several times now I have gone to add data to Firestore, created a new record and added several fields individually only to find upon reloading the page that my authentication token must've been expired and…
2 votes -
Build direct CI/CD
I would love It if the platform enables me to develop and test my code seamlessly and enable me to deploy to different cloud services seamlessly.
3 votes -
Firebase SDK for compose-multiplatform that can support Android, iOS, Web and Desktop
As compose-multiplatform now supports iOS app development hence compose may see a very good in-take by the developers in the near future. The way Firebase Flutter SDK got introduced in a similar way if SDK for compose-multiplatform can be introduced for the developers then it will be super beneficial for them.
7 votes -
IDX: Pull to reveal terminal
VS code provides this feature where you can pull from the bottom to reveal the terminal
3 votes -
Custom quality control for "latest release"
Latest Release is a very useful functionality. For us, even when we have crashes that are worth hot-fixing, it shows as successful. It must go terribly wrong in order to see "Needs investigation" label. This is because these thresholds are hard-coded. It would be great to configure these thresholds
7 votes -
Futures feature
Values which should be computed only when outputting data, can be stored as futures.
7 votes -
Wildcard index exemptions
Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.
We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.
In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.
It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.
We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index…
6 votes -
1 vote
- Don't see your idea?