Skip to content

fix: reject 'cwd' key in integration-suites with a clear error#53

Closed
javierdelapuente wants to merge 1 commit into
mainfrom
fix/remove-cwd-support
Closed

fix: reject 'cwd' key in integration-suites with a clear error#53
javierdelapuente wants to merge 1 commit into
mainfrom
fix/remove-cwd-support

Conversation

@javierdelapuente
Copy link
Copy Markdown
Collaborator

Summary

The cwd key in integration-suites was renamed to working-dir in #50. Previously, a stale cwd: entry in spread.yaml would silently pass through to spread as an unknown key.

Changes

  • _build_suite_entry now raises ConfigurationError immediately if cwd is found, with a message directing users to working-dir
  • Extracted _pop_opcli_keys helper to keep _build_suite_entry under the C901 complexity limit
  • Added test test_cwd_key_raises_configuration_error in TestExplicitSuiteValidation

The 'cwd' key was renamed to 'working-dir' in #50. Previously a stale
'cwd:' entry in spread.yaml would silently pass through to spread as an
unknown key. Now _build_suite_entry raises ConfigurationError with a
migration message directing users to 'working-dir'.

The opcli-key extraction is refactored into _pop_opcli_keys to keep
_build_suite_entry under the C901 complexity limit.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@javierdelapuente
Copy link
Copy Markdown
Collaborator Author

Closing — the code already has no cwd support after #50. No changes needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant