-
-
Notifications
You must be signed in to change notification settings - Fork 368
docs: Add FVM instructions in README #6464
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
base: develop
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #6464 +/- ##
==========================================
- Coverage 9.54% 5.87% -3.68%
==========================================
Files 325 496 +171
Lines 16411 29549 +13138
==========================================
+ Hits 1567 1737 +170
- Misses 14844 27812 +12968 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There's no |
I wouldnt say it’s meaningless because it addresses a point people repeatably have issues with. However, the benefit does increase if we have this configuration file as well. @TapItNinja could you add that? Thanks |
I'm sorry, but no. Is-there an issue to discuss this? -> No. FVM only works with a configuration folder. |
I'm not sure I follow what you are saying because the documentation explicitly says:
And I had the impression that basically every week somebody ask in the slack how to run the project and the proposed solution was usually to downgrade flutter. |
@g123k @github-throwaway Thank you for your feedback. You've raised a valid point about the FVM configuration. While the README instructions provide clear guidance, I understand the desire for a more comprehensive setup. Key points:
Proposed next steps:
Would you like me to draft a minimal |
What
Screenshot
N/A (this is a text-only change to the README)
Fixes bug(s)
Part of