30 results found
-
add persistent Git login
Have global keys and config for git without log in every time you make a new project, also bumping the custom git configuration. Then you can one-click import repos from any git server configured.
5 votes -
integration and compatible with vscode
I request that since both vscode and idx have very very similar ui i just wish that my settings will easily export from one to another like both of them have "code runner" extension by "Jun Han" in vscode marketplace and by "formulahendry" in idx if i change anything in settings my shortcuts and so on in this extensions or rather in general i wish im able to easily access my files from github( since every devceloper uses it) or even google drive, local file directory or any other thing i should be able to sync all my settings, extensions,…
5 votes -
Allow generating an .idx file after already initializing a project
I want to "Enable Nix for this workspace" after the fact, say if I have created or imported a new IDX project. I note that it appears I can manually create a
.idx/idx.jsonfile.5 votes -
GitHub account management
Hi, if I checkout a github repo that is public, but that I own and want to make changes to, I am not prompted for my GitHub credentials and therefore don't have write permissions to the repo. Would be good to have proper GitHub account management included in the experience (not only when you start the project)
17 votes -
Ability to saved custom made dev.nix configs for future projects
Since IDX is using nix files to configure an environment, it would probably be best for us to create and save these files and be able to import it into another/future project.
Specifically "imported from repos" and blank workspaces. That way we wouldn't have to recreate the file or save it in another place when you can just access it from IDX itself.
2 votes -
Support for user-specific config (user.nix) in addition to dev.nix
IDX now has project-specific
.idx/dev.nixfile, which configures the project-specific environment.I'd like to have a user-specific
user.nix(or similar) file which would be applied on all of my own workspaces, which would not be shared to other people using my project.Use case: I author an open source project, which needs project level dependencies. These I'd put to
.idx/dev.nix. I also have a ton of terminal and git aliases and configs that I'd like to have on my own projects, but which don't make sense in the context of my open source project.2 votes -
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.
20 votes -
share to group emails or aliases and permissions
for now, cant share to group emails or aliases. And also cant edit permissions such as edit, comment, viewer.
1 vote -
Support more share ACL types like sharing to mailing list
Sharing to a specific person's email works. Sharing to a mailing list doesn't work currently.
2 votes -
1 vote
- Don't see your idea?