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
LHR configSettings.output can be either a string or a list. For convergence with proto it needs to be one or the other.
configSettings.output
The text was updated successfully, but these errors were encountered:
it's always an array from the CLI, so we'd just need to correct the module uses. It's marginally more annoying to use an array there, but not so bad.
It looks like all the client entry points all use the string version, and we'd need to update the default in constants.js.
constants.js
Sorry, something went wrong.
I'd also argue if we're converting it to always array that we should change the name to reports :)
reports
exterkamp
Successfully merging a pull request may close this issue.
What is the current behavior?
LHR
configSettings.output
can be either a string or a list. For convergence with proto it needs to be one or the other.The text was updated successfully, but these errors were encountered: