FuelLabs/fuel-core

Identify all the places we are using `anyhow` on trait interfaces

Open

#2,592 opened on Jan 16, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (57,084 stars) (2,861 forks)batch import
good first issue

Description

We need to know all the places before we can identify the work to do.

Contributor guide

Tech stack
rust
Domain
backend
Issue type
research
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 Rust knowledgegrep or ripgrep usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Use grep or ripgrep to search for 'anyhow' or 'anyhow::Error' in all Rust source files under the src/ directory. Focus on trait definitions and implementations. List each occurrence with file path and line number. This will help in planning a refactoring to replace anyhow with custom error types.