You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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