Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to soft error mechanism #4

Open
Etua opened this issue Jan 30, 2020 · 0 comments
Open

Improvements to soft error mechanism #4

Etua opened this issue Jan 30, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@Etua
Copy link
Owner

Etua commented Jan 30, 2020

Currently there are only two categories of "soft" errors which can be discovered in processing individual files that do not affect processing other files. One of them is expected during standard usage (skipping of fpcalc for unsupported files) whereas the other may be a result of no Internet connection which for now will result in skipping every step after downloading JSON leaving target directory empty.

Right now their only indicators are printed messages for CLI mode. I think that some type for listing errors should be defined with typedef so even success messages would contain complete information like "X files moved. Y files skipped because of unsuitable type. Z files skipped because of network errors." That way it would be easier to add other error types in the future.

@Etua Etua added the enhancement New feature or request label Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant