-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
implement '-e/--error-file' command-line option (#4732)
copying per-URL options from regular, read-only input files does currently not work
- Loading branch information
Showing
3 changed files
with
61 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
99b7662
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this
--error-file
option already supported for usage in the config file? Or will be?99b7662
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not and it was never intended to, as I thought of it as similar to
--input-file
.I guess you'd like me to add it as a global config file option?
99b7662
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see what you mean.
--error-file
is designed to be used together with--input-file
, for users who do not set up logging output in their config, right?Or, alternatively, if you supply multiple URLs (dozens, maybe) on the command-line, you can "log" failing URLs of this input via
--error-file
, correct?Now that I think about it,
--error-file
does apparently not do anything differently (or anything more) than a proper logging configuration - which I already use.Okay, simply forget my comments here and keep it as it is..
99b7662
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having a designated file for input URL errors is better than having to comb through the general logging output I think, so I added this option anyway. 042a9da
Maybe I should make this part of the same mechanism as
--write-unsupported
...99b7662
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I agree..
Maybe, I can't really make any judgement here from the implementation's perspective.
On the other hand, right now we have
output.unsupportedfile
, which can be either of typePath
or a logging config object, withpath
as the property here to point to the actual unsupported output file, so we cannot usepath
again here, using a different identifier name (likepath-errorfile
or whatevs) would be kinda inconsistent, so, at least in the config, it would have been it's ownoutput.errofile
, which is now a matter of fact anyway with 042a9daI don't really know where I'm going here actually.. I realize the structure of the config can be pretty much completely independent from the details of the actual implementation.