Skip to main content

StrategyConfigChange

One difference between two versions' configuration.

before and after are JSON-encoded, so one type carries a number, a string, a boolean or a whole condition sub-tree without the schema naming each shape. The side on which the path is absent is null — which is what keeps ADDED and REMOVED distinguishable from a change to or from JSON null.

type StrategyConfigChange {
  section: StrategyConfigSection!
  path: String!
  kind: StrategyConfigChangeKind!
  before: String
  after: String
}

Fields​

StrategyConfigChange.section ● StrategyConfigSection! non-null enum​

StrategyConfigChange.path ● String! non-null scalar​

Dotted path into the configuration. Indicators are addressed by their stable id rather than list position ("indicators[rsi_1].params.period"), because the builder reorders that list whenever one is inserted and a positional path would move under a reader's feet.

StrategyConfigChange.kind ● StrategyConfigChangeKind! non-null enum​

StrategyConfigChange.before ● String scalar​

JSON-encoded value on the base version, null when the path is absent there.

StrategyConfigChange.after ● String scalar​

JSON-encoded value on the target version, null when the path is absent there.

Member Of​

StrategyVersionComparison object