Repository navigation
Add a project upgrade mechanism #12573
Description
Activity
- added this to the milestone
on Oct 17, 2017 I'm currently targeting explicit Dart awareness of Flutter revision numbers and applying direct file changes.
Maybe one day in the future, it might be worth exploring a automatic codeless way of maintaining and auto applying diffs on various versioned .yaml/.json/.xml/.etc templates but so far, the use cases lean more towards direct targeted changes.
Worth explicitly noting that this will need to support interactive steps with confirmation. In #18102 (migrate iOS devicelab tests to universal binaries), supporting migration came up, but there are some (probably rare) cases where an app may legitimately be 64-bit only, so I think we'd want to confirm before updating.
I great first step would be a version number stored with the generated files and
flutter doctorreporting if the projects generated files are up-to-date
(even without providing an automated way to upgrade them).I created https://github.com/flutter/flutter/wiki/Workarounds-for-common-issues#generated-project-files-outdated and this seemed to help quite a few times already.
Reacted by Ats UiboupinOnly partly related. This is about dealing with all kinds of changes in the user projects when the Flutter framework version changes. #9827 is about dealing with the pod environment in the user project when the user adds/removes plugins or wants to customize. That can be within the same Flutter framework version or different.
- modified the milestones: ,
on Jan 7, 2020 - modified the milestone:
on Jun 1, 2020 - removed this from the milestone
on Jun 16, 2020 - removed this from the milestone
on Jul 7, 2020 - modified the milestone:
on Jul 22, 2020 - removed this from the milestone
on Aug 17, 2020 This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 13, 2021
We often make changes to the default
flutter createtemplate. It would be good to have an automated upgrade mechanism that takes various existing native code, yaml, artifacts etc and apply the latest changeflutter createleave some sort of version stamp in the produced artifacts indicating the version of the tool when the project was createdflutter project upgradecommand that takes in a number of 'steps' recipes in a folder that does modifications gated by version comparison conditions. This should warn the users to keep their git working directory clean before proceeding.