Skip to content

Phase 1: correctness fixes - #160

Merged
shunichironomura merged 1 commit into
mainfrom
sn-branch-1
Apr 17, 2026
Merged

Phase 1: correctness fixes#160
shunichironomura merged 1 commit into
mainfrom
sn-branch-1

Conversation

@shunichironomura

@shunichironomura shunichironomura commented Apr 17, 2026

Copy link
Copy Markdown
Member
  • Use char-safe truncation in Event::description() for NoteAdded to
    avoid panicking on multi-byte UTF-8 (e.g. Japanese notes).
  • Reject non-string / non-{min,max} values for the 'expected' field
    in input definitions instead of serialising Rust debug output as
    the expected value.
  • Rename ExecutionError::DuplicateStepHeading to DuplicateStepId so
    the variant name matches the actual uniqueness check on step IDs.
  • Handle the Active and Finished states explicitly when applying a
    second ExecutionStarted event, returning AlreadyFinished instead
    of the misleading AlreadyStarted.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com


This is part 1 of 5 in a stack made with GitButler:

- Use char-safe truncation in Event::description() for NoteAdded to
  avoid panicking on multi-byte UTF-8 (e.g. Japanese notes).
- Reject non-string / non-{min,max} values for the 'expected' field
  in input definitions instead of serialising Rust debug output as
  the expected value.
- Rename ExecutionError::DuplicateStepHeading to DuplicateStepId so
  the variant name matches the actual uniqueness check on step IDs.
- Handle the Active and Finished states explicitly when applying a
  second ExecutionStarted event, returning AlreadyFinished instead
  of the misleading AlreadyStarted.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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