ordinals/ord

[enhancement] In `ord.yaml` specifying options for subcommands

Open

#3,818 opened on Jun 11, 2024

View on GitHub
 (1 comment) (2 reactions) (0 assignees)Rust (1,479 forks)github user discovery
enhancementgood first issue

Repository metrics

Stars
 (3,955 stars)
PR merge metrics
 (Avg merge 15d 21h) (5 merged PRs in 30d)

Description

Hello,

I think about adding subfields into ord.yaml file for subcommands options'.

Maybe something like this:

wallet: {
    name: "MyWallet",
    no-sync: false
}

I don't know what should be modified from src to integrate such options, but it can simplify some commands.

Contributor guide

Research direction
Examine the current ord.yaml parsing logic in src/subcommand.rs or src/yaml.rs. Look for how existing global options are parsed and consider adding nested structures for subcommands like wallet. Use serde to deserialize a hierarchical config and merge with CLI args. Test with an example config file.
Tech stack
rust
Domain
cli
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-2 days
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
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50