Skip to content

[plan] Align additionalProperties and enum values between schemas #11711

@github-actions

Description

@github-actions

Objective

Resolve additionalProperties conflict and enum value mismatch between main and MCP config schemas.

Context

From discussion #11706:

  • additionalProperties conflict: Main schema uses true (permissive), MCP config uses false (strict)
  • Enum mismatch: Main schema includes "remote" in type/mode enums, MCP config doesn't

Approach

  1. Investigate which additionalProperties setting is correct for workflow validation
  2. Align both schemas to use the same setting
  3. Determine if "remote" is valid for type enum or should be removed
  4. Document the decision in schema comments

Files to Modify

  • pkg/parser/schemas/main_workflow_schema.json - Update additionalProperties and/or enum values
  • pkg/parser/schemas/mcp_config_schema.json - Update to match (if needed)

Acceptance Criteria

  • additionalProperties setting is consistent between schemas
  • Enum values for type/mode are identical
  • Decision documented in schema comments
  • Existing workflows continue to validate correctly
  • Run make build to embed updated schemas
  • All tests pass with make test

AI generated by Plan Command for discussion #11706

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions