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 (13,906 stars) (2,725 forks)batch import
P2good first issuekind/enhancementtopic/bootcamp

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

Tech stack
go
Domain
backendtooling
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-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingIPFS configuration conceptsOptional type pattern
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Start by reading through issue #151 in the go ipfs config repository to understand the optional types implementation. Then enumerate all config keys in Kubo's config.go and related files. For each key, check if it can be migrated to use optional types, and document the changes needed. Consider asking maintainers for clarification on priority keys if needed.