You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: