We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
app.js
parser.addArgument( ['-p', '--prettyPrint'], { help: 'Pretty print JSON output. The -o/--output should be raw-json/json/cxf.', action: 'storeTrue' } )
parser.js
const out = (prettyPrint === 'true') ? JSON.stringify(rawJson, null, 2) : JSON.stringify(rawJson)
This seems incorrect as prettyPrint will be interpreted as a Boolean, not a string.
prettyPrint
parser.addArgument( ['-d', '--directory'], { help: 'Specify output directory, with the default being the current.', defaultValue: 'current' } )
Why the string current is used for the current directory as opposed to . or ./? This requires conversions such as: lib/cxfExtractor.js
current
.
./
lib/cxfExtractor.js
if (directory === 'current') { directory = '' }
At least such conversions should be made once and for all in app.js and each function should rather use OS common pathnames.
The text was updated successfully, but these errors were encountered:
anandkp92
No branches or pull requests
app.js
parser.js
This seems incorrect as
prettyPrint
will be interpreted as a Boolean, not a string.app.js
Why the string
current
is used for the current directory as opposed to.
or./
?This requires conversions such as:
lib/cxfExtractor.js
At least such conversions should be made once and for all in
app.js
and each function should rather use OS common pathnames.The text was updated successfully, but these errors were encountered: