temporalio / temporalio/features
[Feature Request] Harness history checker should have easier way to ignore new fields
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
The features harness supports checking histories against static, in-repo saved histories. This is nice to ensure some form of backwards compatibility, but it easily breaks on genuinely compatible things too, like adding new fields to history events that aren't critical to replay.
Describe the solution you'd like
An easy way to mark certain fields as "it's ok if this is present in current history and not in stored static history"
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the harness history checker and its comparison between current history events and stored static histories. Define how fields can be marked as optional when newly present, while differences in critical fields still fail compatibility checks. Done means compatible added fields can be ignored without weakening other history validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100