Skip to main content

validateScheduleScenario

8.0.0 engine API transition

This method is a candidate for removal from production governors and engine exports at 8.0.0. Its 7.x route has not been removed. Final removal and standalone package-export decisions require the per-method review and external-integrator confirmation described in the transition index.

Source-local contract​

The declaration below is copied from the pinned source revision; referenced types are defined there. It is an implementation signature, not a package import example.

/**
 * Shape + light referential validation for a {@link ScheduleScenario}.
 * Placement matchUp/court existence is validated against the live schedule at
 * projection time (Phase 1); here we guarantee a well-formed, commit-ready
 * object and that every placement targets a known tournamentId (when
 * tournamentRecords are supplied).
 */
export function validateScheduleScenario({ tournamentRecords, scenario }: ValidateScheduleScenarioArgs): {
  valid: boolean;
  error?: any;
  info?: string;
};

Engine effects​

State writes: not yet assessed. Notices: not yet assessed. Governor query/mutate placement is not proof of purity; review the implementation and engine path before deciding exposure.

Consumer evidence​

The refreshed source-name scan found no name mentions in the scanned product source files. This does not establish external-integrator non-use. The manifest records repository revisions and scan exclusions. External-integrator confirmation is pending.

Availability and ownership​

  • Production governor declarations: scheduleGovernor.
  • Standalone package API after 8.0.0: decision pending; this page does not establish a supported import.
  • Implementation: src/validators/validateScheduleScenario.ts — validateScheduleScenario. Source paths and aliases are not package import paths.
  • Replacement workflow: not yet established; no supported replacement is promised.
  • Test-only adapters: may exercise this implementation independently of production engine exports; this is not evidence of product use.

Preserved 7.x reference​

The passages below preserve the existing governor documentation. Engine examples describe 7.x availability, not an 8.x replacement. Source contracts take precedence where an explicitly noted correction applies.

From governors/schedule-governor.md​

Shape + light referential validation for a scenario object (used internally by add/update).

engine.validateScheduleScenario({ scenario }); // → { valid: boolean, error?, info? }