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
Since I use flutter fvm, all packages that are in the yaml file are technically appearing in my folders since I assume your tool looks everywhere in the project, also the .fvm folder which includes all the downloaded packages that I'm using. So even though a dependency is not used in my lib folder it does not show as an unused dependency. Could you make a configfile to set folder in which your tool should look for appearances of dependencies?
The text was updated successfully, but these errors were encountered:
I appreciate your feedback. Let me clarify how the tool works and address your concerns:
fvm is used for managing Flutter versions and does not directly manage your project's dependencies. Your project's dependencies are listed in the pubspec.yaml file at the root of your project. The tool reads this file to get the list of dependencies and then checks the lib/ folder to see if any of these libraries are imported at least once.
I'll consider this feature request for a future update (custom pubspec.yaml path).
In the meantime, please ensure that only the necessary folders, like lib/,
are being included in your analysis to reduce false positives.
If I've misunderstood your issue or if you have additional suggestions, please let me know!
Thank you for your understanding and cooperation.
Since I use flutter fvm, all packages that are in the yaml file are technically appearing in my folders since I assume your tool looks everywhere in the project, also the .fvm folder which includes all the downloaded packages that I'm using. So even though a dependency is not used in my lib folder it does not show as an unused dependency. Could you make a configfile to set folder in which your tool should look for appearances of dependencies?
The text was updated successfully, but these errors were encountered: