redhat-et / redhat-et/ProtoBot
Implement Validation Rules and an in-memory WMS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 6
- Avg merge
- 23h 24m
- Merged PRs (30d)
- 66
Description
Scope
Implement the MVP lifecycle Validation Rules and an in-memory WMS test adapter. The adapter must exercise request/work-item state without coupling the domain rules to GitHub.
Cover expected state, contract version, authorization context, leases/fencing where applicable, idempotent materialization, and structured rejection.
Dependencies
- #31 and #32 contracts.
- #30 for the caller-facing diagnostic shape.
Acceptance criteria
- Valid and invalid lifecycle transitions are covered by a table-driven test matrix.
- Stale writes and duplicate claims fail without mutation.
- Replayed materialization and completion operations return the original result.
- The in-memory adapter proves the Drafting Table operation set is disjoint from Job Site execution operations.
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 reading the contracts in issues #31 and #32 and the caller-facing diagnostic shape in #30. Define the table-driven lifecycle transition tests and the in-memory WMS adapter around those contracts. Done means stale writes and duplicate claims reject without mutation, replays return original results, and Drafting Table operations remain disjoint from Job Site execution operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100