Detect message type pointer mismatches that cause a dispatch to be ignored.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
When:
- a message is being dispatched via the test runner
- and there are no routes for that message type
- but there IS a route for a pointer-to-that-type (or vice-versa)
The assertion suggestions should indicate that a "similar route" exists, similarly to how it does when comparing messages in MessageAssertion.
Contributor guide
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 in the test runner's assertion-suggestion path and compare its behavior with MessageAssertion, which already handles similar message comparisons. Trace the no-route case for a message and its pointer counterpart, then verify that the suggestion identifies the similar route when either form is registered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100