sharedBuildFlags top-level property
Flags shared by the outer revali build and the construct runner's
build. recompile is outer-only and is never forwarded.
Implementation
final sharedBuildFlags = <ConstructFlag>[
_flavor,
const ConstructBoolFlag(
name: 'release',
help:
'(Default) Whether to run in release mode. '
'Disables hot reload, debugger, and logger',
),
_profile,
// No default, and that is the fix: it used to default to `build`, which
// skips every construct, so a plain `revali build` never regenerated the
// client and no CI-shaped build could reproduce a client-generation defect.
// Absent now means BOTH phases. Passing it still selects a single one, which
// `revali_docker` relies on — it writes `--type constructs` into the
// Dockerfiles it generates, and those live in users' repos long after they
// are generated. Visible for the same reason: it appears in a file people
// read.
ConstructOption(
name: 'type',
help:
'Generate a single phase. '
'Omit to generate constructs and then build.',
allowed: GenerateConstructType.values.map((e) => e.name),
allowedHelp: {
for (final type in GenerateConstructType.values)
type.name: type.description,
},
),
_dartDefine,
_dartDefineFromFile,
];