-
Notifications
You must be signed in to change notification settings - Fork 137
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
Too Verbose #154
Comments
Try passing Feel free to reopen if this is still a problem. |
This is my initializer: Parse.init :application_id => ENV['PARSE_ID'],
:api_key => ENV['PARSE_KEY'],
:master_key => ENV['PARSE_MASTER_KEY'],
:quiet => true |
Not sure then. (reopening...) |
Because quite config is in master only, not release yet. Here is the commit 618b551. |
Bingo! If you want to use this feature now, change your gemfile to point to the master branch and run |
@adelevie I think you should release new version (say |
I think in the meantime, until the new version is released, you can reduce the logs by setting a new Logger in the initializer, and make it log only warnings or more severe messages: Parse.init application_id: 'APPLICATION_ID',
api_key: 'API_KEY',
logger: Logger.new(STDERR).tap { |logger| logger.level = Logger::WARN } |
honestly, this is probably a better solution because my original fix silences all logging. Would love to get an elegant solution to passing in like, loud, quiet, silent for log level. |
My tests end up with extra logs all over even though quiet is set to true.
The text was updated successfully, but these errors were encountered: