Skip to content

Fix config.schema.json mismatches + add parity test #57

Description

@wbreza

Architecture Context

The JSON Schema at schemas/config.schema.json has drifted from the Go source of truth in internal/projectconfig/config.go. Three mismatches exist: token defaults (2500/2000 in schema vs 500/1000 in code), server.resultsDir ("." vs "results/"), and the StorageConfig section is completely missing from the schema. Add a Go test that asserts parity between schema defaults and code defaults to prevent future drift.

Architecture doc: docs/init-config-consolidation/architecture.md
Parent epic: #20

Acceptance Criteria

  • schemas/config.schema.json tokens.warningThreshold default is 500 (matches config.go:35)
  • schemas/config.schema.json tokens.fallbackLimit default is 1000 (matches config.go:36)
  • schemas/config.schema.json server.resultsDir default is "results/" (matches config.go:29)
  • schemas/config.schema.json includes a storage section with provider, accountName, containerName (default "waza-results"), and enabled fields (matches config.go:100-105)
  • A new Go test loads the JSON Schema, extracts defaults, and asserts they match projectconfig.New() values
  • go test ./... passes; golangci-lint run passes

Metadata

Metadata

Assignees

Labels

epic:go-cliE1: Go CLI FoundationgoPull requests that update go codepriority:p0Blocking release

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions