Add report suggestion when an app contains message types that differ only by pointer/non-pointer.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
For example, if within a single app, one handler uses the message type Foo{} and another uses the message type &Foo{} this should produce some kind of "warning" suggestion at the test level.
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
No files or tests are named. Start by locating the test-level report suggestion handling in the Go testkit and inspect how message types are compared; reproduce an app containing handlers for Foo{} and &Foo{}. Done means the test-level report emits a warning suggestion for pointer/non-pointer variants within one app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100