feat(req)!: `I` should be encapsulated with `I()`
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Instead of adding comments to instruct how changing `req.I` is forbidden. It should be made private and only allowed access by calling function `req.I()`
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 locating the request type and all references to req.I in the repository. Check the existing tests for request behavior, then verify that the field is no longer directly accessible and that callers use req.I() instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100