Maybe a HTTP client channel should advise on questionable recv patterns
Open
enhancement
- Dominant language
- Go
- Stars
- 8
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Say a `revc` pattern for an HTTP client references `statusCode` instead of `statuscode`, which is what's used. Maybe the channel should issue a (runtime) warning -- with some option to suppress those warnings?
Contributor guide
Assessment
This issue has not been assessed yet.