Permalink
Browse files

Updated a bunch of pod with new info log type

  • Loading branch information...
Ovid Alexis Sukrieh
Ovid authored and Alexis Sukrieh committed Mar 27, 2012
1 parent 52b630a commit 0404bc36e2541b6073109834d4b835739a6347ed
Showing with 18 additions and 16 deletions.
  1. +4 −2 lib/Dancer/Config.pm
  2. +7 −8 lib/Dancer/Cookbook.pod
  3. +6 −5 lib/Dancer/Introduction.pod
  4. +1 −1 lib/Dancer/Logger/Abstract.pm
View
@@ -491,9 +491,11 @@ B<core>, B<debug>, B<warning> or B<error>.
=item B<debug> : all messages are logged
-=item B<warning> : only warning and error messages are logged
+=item B<warning> : only warning, error and info messages are logged
-=item B<error> : only error messages are logged
+=item B<error> : only error and info messages are logged
+
+=item B<info> : only info messages are logged
=back
View
@@ -770,11 +770,12 @@ To enable logging to a file, add the following to your config.yml:
Then you can choose which kind of messages you want to actually log:
- log: 'core' # will log debug, warning and errors, and messages from
+ log: 'core' # will log all messages, including messages from
# Dancer itself
- log: 'debug' # will log debug, warning and errors
- log: 'warning' # will log warning and errors
- log: 'error' # will log only errors
+ log: 'debug' # will log debug, warning, error and info messages
+ log: 'warning' # will log warning, error and info messages
+ log: 'error' # will log error and info messages
+ log: 'info' # will log only info messages
If you're using the C<file> logging engine, a directory C<appdir/logs> will be
created and will host one logfile per environment. The log message contains the
@@ -783,13 +784,11 @@ information (file and line).
=head3 Logging your own messages
-Just call L<debug|Dancer/debug>, L<warning|Dancer/warning> or
-L<error|Dancer/error> with your message:
+Just call L<debug|Dancer/debug>, L<warning|Dancer/warning>,
+L<error|Dancer/error> or L<info|Dancer/info> with your message:
debug "This is a debug message from my app.";
-
-
=head1 RESTING
=head2 Writing a REST application
@@ -398,19 +398,20 @@ start the logger engine in your config.yml
Then you can choose which kind of messages you want to actually log:
- log: 'debug' # will log debug, warning and errors
- log: 'warning' # will log warning and errors
- log: 'error' # will log only errors
+ log: 'debug' # will log debug, warning, error and info messages
+ log: 'warning' # will log warning, error and info messages
+ log: 'error' # will log error and info messages
+ log: 'info' # will log only info messages
A directory appdir/logs will be created and will host one logfile per
environment. The log message contains the time it was written, the PID of the
current process, the message and the caller information (file and line).
-To log messages, use the debug, warning and error methods, for instance:
+To log messages, use the debug, warning, error and info functions. For
+instance:
debug "This is a debug message";
-
=head1 USING TEMPLATES
=head1 VIEWS
@@ -266,7 +266,7 @@ application to die.
=head2 _should
Checks a certain level number against a certain level type (core, debug,
-warning, error).
+warning, error, info).
=head1 AUTHOR

0 comments on commit 0404bc3

Please sign in to comment.