PostGenStep class final

A command the pipeline runs in the generated app after flutter pub get and code generation, such as flutterfire configure.

Steps run in the order of the contributions of a socket (see SocketContribution). The environment of a step includes, in its PATH, the directories of the tools that Preflight checks installed.

A step may continue another step, such as with a fix of a file that the tool of that step writes: it names that step by its id in followUpOf, and runs right after it rather than in its own place. A module continues its own steps and those that the modules it depends on publish the ids of, so a module knows nothing of the modules that continue its steps.

A step whose hosts leave out the operating system of the run does not apply to it. A step that applies runs unless:

• it is external and the run skips external setup (--skip-external-setup);
• it is interactive, or has a notice, and the run cannot ask the user;
• a check that it needs has not passed;
• it continues a step that is not done.

Then the pipeline prints the command for the user to run later, or fails generation if the step is not skippable; a step that continues a step that is not done is left for later with it either way. In a run that can ask, the user may also leave for later a skippable step that continues no other step, and a step with a notice, whether it continues another or not. A skippable step whose tool is missing, or that fails, is left for later too; any other step that fails fails generation.

The app is generated in a temporary directory and moved to its place afterwards, so a step must not write the absolute path of its working directory into the app. The files where Flutter records such paths, like ios/Flutter/Generated.xcconfig, are written again in the app's place.