37f8f6681c
Currently the tool prints problems right as it is checking the code without an intermediate error representation. However for various reasons it would be beneficial to have an intermediate error type: - It makes the code cleaner, having all errors in one place - It allows printing the error in different ways, e.g. for a future --json mode This commit prepares for an incremental refactoring for an intermediate error/problem representation. Most notable is that we want to be able to collect multiple errors/problems and not just exit on the first one. We introduce the type alias CheckResult and CheckError (later renamed to NixpkgsProblem), where CheckError allows collecting multiple CheckErrors using the utility function flatten_check_results (later renamed to check_result::sequence) The write_check_result function is only temporarily introduced to help refactoring, it's removed again in later commits.
20 lines
389 B
TOML
20 lines
389 B
TOML
[package]
|
|
name = "nixpkgs-check-by-name"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
|
|
[dependencies]
|
|
rnix = "0.11.0"
|
|
regex = "1.9.3"
|
|
clap = { version = "4.3.23", features = ["derive"] }
|
|
serde_json = "1.0.105"
|
|
tempfile = "3.8.0"
|
|
serde = { version = "1.0.185", features = ["derive"] }
|
|
anyhow = "1.0"
|
|
lazy_static = "1.4.0"
|
|
colored = "2.0.4"
|
|
itertools = "0.11.0"
|
|
|
|
[dev-dependencies]
|
|
temp-env = "0.3.5"
|