Collect errors instead of failing early #1048
Unanswered
sschuberth
asked this question in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This continues the discussion from here. Instead of failing early / fast e.g. on encoding errors, IMO it would be nice to continue checking remaining files, in order to see how many errors there are in total and / or bulk fix all errors instead of fixing them incrementally.
Both failing early and collecting errors have their valid use-cases. E.g. on CI you sometimes want to fail early to reduce feedback times. However, as lychee runs fast anyway, I feel there's little need to fail early to safe time.
Beta Was this translation helpful? Give feedback.
All reactions