commit | 815de3404dacbd120a2bf2eb407d62107c5f24b4 | [log] [tgz] |
---|---|---|
author | jakemac@google.com <jakemac@google.com> | Fri Jul 25 18:35:00 2014 +0000 |
committer | jakemac@google.com <jakemac@google.com> | Fri Jul 25 18:35:00 2014 +0000 |
tree | 95ff61037d276270037b9997f3ba0ce466f8e3d9 | |
parent | d67fbc62d1c4bf2f884c1b87f678a15fbf11cd20 [diff] |
updated logging package to accept functions or other non-string objects when logging R=sigmund@google.com Review URL: https://codereview.chromium.org//420553007 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/logging@38584 260f80e4-7a28-3924-810f-c04153c831b5
By default, the logging package does not do anything useful with the log messages. You must configure the logging level and add a handler for the log messages.
Here is a simple logging configuration that logs all messages via print
.
Logger.root.level = Level.ALL; Logger.root.onRecord.listen((LogRecord rec) { print('${rec.level.name}: ${rec.time}: ${rec.message}'); });
First, set the root [Level]. All messages at or above the level are sent to the [onRecord] stream.
Then, listen on the [onRecord] stream for [LogRecord] events. The [LogRecord] class has various properties for the message, error, logger name, and more.
Create a [Logger] with a unique name to easily identify the source of the log messages.
final Logger log = new Logger('MyClassName');
Here is an example of logging a debug message and an error:
var future = doSomethingAsync().then((result) { log.fine('Got the result: $result'); processResult(result); }).catchError((e, stackTrace) => log.severe('Oh noes!', e, stackTrace));
When logging more complex messages, you can pass a closure instead that will be evaluated only if the message is actually logged:
log.fine(() => [1, 2, 3, 4, 5].map((e) => e * 4).join("-"));
See the [Logger] class for the different logging methods.