Skip to main content

compareStrategyVersions

Compare two versions of one strategy: what their configuration does differently, and how their backtests came out.

Both ids must belong to the SAME version chain — version numbers are per chain, so a pair from two unrelated strategies would render as a version history that never happened. Comparing a version with itself is allowed and returns no changes, which is what a UI whose two selectors default to the same row should render.

Row-level tenancy is enforced in the resolver with the same readable-workspace set Query.strategies and Backtest.digest use; a version the caller cannot read is reported as not found rather than as denied, so this cannot be used to probe for someone else's strategy.

compareStrategyVersions(
  baseID: ID!
  targetID: ID!
): StrategyVersionComparison

Arguments​

compareStrategyVersions.baseID ● ID! non-null scalar​

compareStrategyVersions.targetID ● ID! non-null scalar​

Type​

StrategyVersionComparison object​

What changed between two versions of one strategy, and whether it helped.