ipfs/kubo

add config validations

Open

#2,491 opened on Mar 21, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
exp/experthelp wanted

Description

We should set up hooks for certain config keys to validate that can be run when the user modifies them.

The validations should also be run during init to make sure that any modifications the user makes directly to the file get validated as well

Contributor guide

Tech stack
go
Domain
backend
Issue type
feature
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingFamiliarity with IPFS configUnderstanding of config validation patternsBasic knowledge of kubo codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Start by exploring the kubo config package (likely in 'config/' directory) to understand the current config structure and any existing validation. Look for any existing hooks or lifecycle methods that could be extended. Review the two comments on the issue for additional context. The goal is to implement validation hooks that run both on config modification (e.g., through a config setter) and during initialization. Identify which config keys need validation and define appropriate validation functions.
add config validations · ipfs/kubo#2491 | Good First Issue