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
I see that here logger is explicitly turned off.
logger
export interface CommanderOptionsType extends Omit<CommandFactoryRunOptions, 'logger'> { pluginsAvailable?: boolean; }
Though it would be really nice if, at least in testing, we could set logger: false so that unneeded lines won't spawn
logger: false
If logger variable was hidden for a reason, maybe there's an option to pass false to it still? Or come up with another variable?
false
No response
Would be nice to write tests with expected errors that don't clog the console
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I see that here
logger
is explicitly turned off.Though it would be really nice if, at least in testing, we could set
logger: false
so that unneeded lines won't spawnDescribe the solution you'd like
If
logger
variable was hidden for a reason, maybe there's an option to passfalse
to it still? Or come up with another variable?Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Would be nice to write tests with expected errors that don't clog the console
The text was updated successfully, but these errors were encountered: