Unify package choice for human-readable formats
Open
Nobody has claimed this yet.
dependencies
good-first-issue
- Dominant language
- Go
- Stars
- 131
- Forks
- 16
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 11
Description
Like I've noticed here we use several packages for the same purposes and funtionality.
We'd better stick with only one package.
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 with the discussion in PR #6 linked from the issue, then inspect the repository for the packages used to handle human-readable formats. Identify the overlapping functionality and the affected call sites. Done means the project consistently uses one package for that purpose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100