Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Specify path for .fvm directory #696

Open
supposedlysam-bb opened this issue Mar 21, 2024 · 0 comments
Open

[Feature Request] Specify path for .fvm directory #696

supposedlysam-bb opened this issue Mar 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@supposedlysam-bb
Copy link

Problem Statement

Is your feature request related to a problem? Please describe.
In version 2 and in version 3 of fvm I've experienced issues where CLI tools and the VSCode debugger itself will act on the flutter code through the .fvm directory.

For instance: when debugging my Flutter project in VSCode with "Debug My Code" on and "All Exceptions" checked, it will still show me errors inside of the flutter code. Note: I DO NOT have "Debug My Code + Packages + SDK" turned on.

I've also experienced issues with recursive features of CLI tools including the very_good_cli.

Proposed Solution

Describe the solution you'd like
I'd love to have an option in the .fvmrc file to add a path (relative or absolute) for the .fvm directory so I can specify that it lives somewhere outside of my project.

.fvmrc with directory path

{
  "flutter": "3.19.3",
  "fvmPath": ".."
}

With the addition of this change I could move my project into another folder and have the .fvm directory live there.

Prior to Change

.
├── my_project

After the Change

.
├── my_project_workspace
│   ├── .fvm
│   ├── my_project

Considerations

Describe alternatives you've considered
I've considered reaching out to the maintainers of each tool I use and report the problem, but if I were able to move the location of the .fvm folder so it's outside of my project I wouldn't need to do this in the future.

@supposedlysam-bb supposedlysam-bb added the enhancement New feature or request label Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant