You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works if the logging level for the app is also set to logging.INFO, but as soon as the app’s log level is set to logging.DEBUG, even with the second line added, sanic_cors level became debug.
This is mostly a nuisance, as I do need to enable debug for the main app for development, but the excessive debugs output by sanic_cors is making it very difficult for me to see the messages that I need.
Is there a way around it ? Thanks!
The text was updated successfully, but these errors were encountered:
Hi @smlbiobot
Thanks for opening this issue.
The documentation is left-over from when Sanic-Cors was ported from Flask-Cors.
Most of the documentation is still Flask-Cors specific, and some of it does not apply to Sanic-CORS. Documentation is still a work in progress.
I know currently the output level for Sanic-CORS is tied to the output level of Sanic, that is a limitation of the Sanic-Plugins-Framework, and it a feature that I'd like to get implemented when I get time.
Sounds good — hope you can resolve / update it. The output it generates is very excessive and I sometimes had to turn off sanic debug mode so that I can actually see what is happening.
Based on your documentation, I should be able to force sanic-cors to show only logs at
INFO
level like this:This works if the logging level for the
app
is also set tologging.INFO
, but as soon as the app’s log level is set tologging.DEBUG
, even with the second line added,sanic_cors
level became debug.This is mostly a nuisance, as I do need to enable debug for the main app for development, but the excessive debugs output by
sanic_cors
is making it very difficult for me to see the messages that I need.Is there a way around it ? Thanks!
The text was updated successfully, but these errors were encountered: