-
Notifications
You must be signed in to change notification settings - Fork 13
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
libzeug should not directly write to console #71
Comments
lanice
added a commit
that referenced
this issue
Jul 21, 2014
lanice
added a commit
that referenced
this issue
Jul 21, 2014
lanice
added a commit
that referenced
this issue
Jul 21, 2014
lanice
added a commit
that referenced
this issue
Jul 22, 2014
lanice
added a commit
that referenced
this issue
Jul 22, 2014
lanice
added a commit
that referenced
this issue
Jul 25, 2014
lanice
added a commit
that referenced
this issue
Jul 25, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Especially in the property deserializer, but in general too.
As a user of a library, I want to customize which outputs I show on the console and which not. Libraries should not directly generate output, instead error callbacks should be provided, so that the user can either ignore them or send them to the console if he wishes to.
The text was updated successfully, but these errors were encountered: