Rustcan API Library is too noisy in stdout

Description

Contributor guide

Tech stack

rust

Domain

apicli

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.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Basic knowledge of RustUnderstanding of CLI vs library contexts

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75

Research direction

Investigate how the library currently prints to stdout (likely via println! or similar in lib.rs). Determine a method to detect whether the code is running as a library (e.g., no command line arguments) or as the CLI binary. Implement conditional printing so that library calls are silent unless a verbose flag is set. Look at how other Rust libraries handle this, such as using the log crate with a no op logger by default.