Provide better feedback about failed message dispatches in Call().
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
For example, if you call Test.CommandExecutor().ExecuteCommand() with a message that is not used by the application, you get a rather cryptic panic with the message invalid message role: .
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 by reproducing the failure through Test.CommandExecutor().ExecuteCommand() with a message unused by the application, then trace how Call() handles the failed dispatch. The work is complete when that case reports useful feedback instead of the cryptic "invalid message role: " panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100