1838 results found
-
8 votes
-
Support Jupyter Notebooks and Python/R
Adding support for Jupyter Notebooks and customized Python/R kernels will enable data scientists to develop data and machine learning projects easily in IDX.
23 votesThis is a great suggestion! We are going to investigate what support here can look like and follow-up with you further for more details.
-
An automated way to create test cases
Enable developers to use code script as an input and create test cases of this code script.
1 vote -
Add Support for common ML and Data analysis workloads
Development around Machine Learning and/or tools for performing ML should also be considered well, specifically around building tools for ML which do not directly involve training (such as experiment tracking, data analysis, etc.)
43 votesThis is a great suggestion! We are going to investigate what support here can look like and follow-up with you further for more details.
-
Review the revoke token from apple functionality
I'm implementing a Login with Apple and everything went smooth until I had to delete the account. According to Apple guidelines I need to revoke the token. However, in the Firebase documentation it says I should implement the following:
Auth.auth().revokeToken(withAuthorizationCode: authCodeString)
But the revokeToken method is no longer available. I haven't found yet a way to do it.
Thanks,
Jose
1 vote -
Review the revoke token from apple functionality
I'm implementing a Login with Apple and everything went smooth until I had to delete the account. According to Apple guidelines I need to revoke the token. However, in the Firebase documentation it says I should implement the following:
Auth.auth().revokeToken(withAuthorizationCode: authCodeString)
But the revokeToken method is no longer available. I haven't found yet a way to do it.
Thanks,
Jose
1 vote -
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.
59 votesWe are actively working on addressing these items. Stay tuned for some updates here.
-
Share a Custom Template with Others
When you create a custom template, we want to explore ways of making it easy for you to share it with others in your team or publicly.
21 votes -
Global Installation of Common Build Tools
Various scripts in a project may require build tools like pnpm, npm, gacutil, etc. to be present globally to help build and run the code in your project. Today, Project IDX doesn’t support global installations.
6 votes -
Better Debugging Support for Web Projects
We want to make identifying (and fixing!) issues in code as natural as it can be, fully from inside your browser without any additional configuration.
26 votesThanks for this feedback! We are actively working on this right now and will share updates (and working implementations!) shortly.
-
Persist Environment Settings Across Sessions
If you customize your panels, themes, fonts, colors, and other settings, we want to ensure your customizations are persisted the next time you access Project IDX.
168 votesAs part of our recently released preview of our Nix extensibility work, we persist all changes in your home directory. We are exploring additional ways of being able to persist changes between VM sessions.
-
Support Multiple Projects/Folders
You may have separate projects (with their own build process, etc.) that you still want to see and control from inside the same workspace. This type of project structure is one we want to better support.
95 votesWe are actively discussing how to best address this. Stay tuned for some updates here.
In the interim, please comment on what kind of project(s) you are working in what other tools you have found that do a good job here.
-
Support Previewing on Multiple Browsers
We want to provide you with the ability to test your app across multiple popular browsers, including on mobile devices as well.
16 votes -
Mobile Preview Support for Web Apps
Worldwide, many users browse the internet on their mobile devices. We want to make it easier to test your web app more accurately across Android and iOS devices to catch any quirks (differing native UI, varying screen sizes, rendering engine bugs, etc.) the mobile environments may introduce.
17 votes -
Configure logs save location
Configure where the log files for the emulator are saved, instead of poluting the root of the project
2 votes -
Execution ID in logs generated by Firebase Functions v2
Logs generated by Firebase Functions v1 have the property
labels.execution_idthat can be used to correlate logs that pertain to the same execution. However, that property doesn't exist in logs generated by Firebase Functions v2. It's very important for debugging.5 votes -
API Access to Crash and Performance Data.
Provide Crash Free Metric, Performance metrics, Alerts and Insights via API to integrate with existing systems
10 votes -
Add support to register local Cloud Run instances to event arc triggers in local emulators
Cloud Run makes it possible to write functions that are not currently possible to do with Cloud Functions (e.g. when using software not included in Cloud Function system images). It also possible to register Cloud Run instances to direct eventarc events. Cloud Run instances can be run in local device as a docker instance.
Currently it is not possible to register locally running Cloud Run instance to triggers from local firebase emulator and there fore local development and testing is not possible for apps relying custom Cloud Run functions.
2 votes -
Security vulnerability on using SHA-1 weak hash algorithm
Firebase using SHA-1 weak hash algorithm. This is being raised as Security vulnerability. Recommended to upgrade the hash algorithm.
2 votes -
Support Go in Cloud Functions
Go is much more efficient than Python or Js and should be the obvious choice for backend where performance is crucial
34 votes
- Don't see your idea?