pub type FeatureFlagsOutput = FeatureFlagsOutput;Expand description
Concrete feature-flag output contract returned by typed programmatic runs.
Aliased Type§
pub struct FeatureFlagsOutput {
pub schema_version: SchemaVersion,
pub version: ToolVersion,
pub elapsed_ms: ElapsedMs,
pub feature_flags: Vec<FeatureFlagFinding>,
pub total_flags: usize,
pub workspace_diagnostics: Vec<WorkspaceDiagnostic>,
pub meta: Option<FeatureFlagsMeta>,
}Fields§
§schema_version: SchemaVersionFlags output schema version.
version: ToolVersionFallow CLI version that produced this output.
elapsed_ms: ElapsedMsWall-clock analysis duration in milliseconds.
feature_flags: Vec<FeatureFlagFinding>Detected feature-flag findings.
total_flags: usizeNumber of entries in feature_flags.
workspace_diagnostics: Vec<WorkspaceDiagnostic>Workspace-discovery and source-discovery diagnostics for the run. See
CheckOutput::workspace_diagnostics for the full contract.
A flags run walks and parses the project like every other analysis, so
it records the same discovery kinds: a skipped-large-file,
skipped-minified-file, or source-read-failure file was never
scanned for flags, and a source-parse-degraded file was scanned from
a partial module. Each is a reason a flag can be missing from
feature_flags[], which is exactly what a consumer reading a
zero-result run needs to know. The analysis-stage kinds appear here
too: the scan correlates flags with dead exports, so it runs the
dead-code analyze pass that records them.
Omitted when empty, so a project with no discovery noise sees no change.
meta: Option<FeatureFlagsMeta>_meta block; see [FeatureFlagsMeta].