ipfs/kubo

Update relevant configuration to use optional types

Open

#8,531 opened on Oct 28, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (2,725 forks)batch import
P2good first issuekind/enhancementtopic/bootcamp

Repository metrics

Stars
 (13,906 stars)
PR merge metrics
 (Avg merge 4d 2h) (28 merged PRs in 30d)

Description

Now that go-ipfs-config supports optional types, we should go through and clean up as much of the existing config to use it so we have a consistent story on defaults, etc.

This work will be easier to do after https://github.com/ipfs/go-ipfs-config/issues/151

The first step is to enumerate the various config keys we want to cleanup.

Contributor guide

Research direction
Review go ipfs config optional types and identify config keys that can be updated for consistency.
Tech stack
go
Domain
backendapi
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Gogit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60