RuleImpact.h header

#include <ew/app/RuleImpact.h>

Namespace ew::app

RuleImpact struct

struct ew::app::RuleImpact

What a rule would say about the project as it stands.

Members

int ew::app::timeline::RuleImpact::examined = 0

How many objects the rule applies to.

std::vector<ew::app::diagnostics::Diagnostic> ew::app::timeline::RuleImpact::violations

The findings it would raise right now, one per object it is unhappy with.

Kept whole rather than counted, because the count is only half the question: a writer who decides the rule is right about the future and wrong about the past needs the actual findings to grandfather, and re-deriving them afterwards would risk a different set.

Functions

RuleImpact ew::app::timeline::previewRule(const ew::core::project::Project &project, const ew::core::timeline::ContinuityRule &rule)

What rule would flag if it were saved now.

Shown before saving, not after. A rule written against a mature project can be right in principle and produce three hundred findings on work already done – and a writer who discovers that from the Conflicts dock has already lost the thread they were following. Knowing the number first is what makes "enforce this from now on" a decision rather than a cleanup.