Skip to content

Cargo: Handle errors properly in cargo-marker #169

@xFrednet

Description

@xFrednet

cargo-marker interacts a lot with other programs or the file system. Therefore, it has to handle numerous Result<X, Y> types. Currently, every error is just mapped to a single ExitStatus enum, that provides very little information. This is not ideal...

  • It might be good to use an existing library for error handling.
  • Errors should provide as much information as possible.
  • Only the CLI part of cargo_marker should "know" what an exit status is.

Metadata

Metadata

Assignees

Labels

A-marker-cargoArea: All things connected to `cargo_marker`C-enhancementCategory: New feature or requestE-good-first-issueParticipation: Good for newcomers

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions