A simplest lightweight logger ever possible. Inspired by Android's logger.
Unlike other solutions, LogArt doesn't require any additional initialization. All you need - is to import logger into your class.
Everything else is already implemented for you.
Logging messages #
In order to log message you don't need to create any logger instance.
Here is an example of logging all kind of messages:
verbose("Widget", "Message"); debug("CheckoutScreen", "Message"); info("Scope", "Message"); warning("Tag", "Message"); error("Test", "Message"); wtf("UnexpectedStuff", "Message");
Or you can log messages using old way:
Log.v("Widget", "msg"); Log.d("CheckoutScreen", "msg"); Log.i("Scope", "msg"); Log.w("Tag", "msg"); Log.e("Test", "test"); Log.wtf("UnexpectedStuff", "test");
That's it :D
The art of simplicity #
As the headline says: LogArt - is the simplest logger ever possible, so it probably won't be as powerful as any other logger. But it doesn't mean LogArt is bad (at least I hope :D).
Anyway, if you have any suggestions on how to improve it - you're welcome to open an issue on GitHub :)
[0.0.2] - 8/12/2019 #
- A second birth of a legend (basically small publishing fixes).
[0.0.1] - 8/12/2019 #
- A birth of the simplest lightweight logger ever possible.
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: logart: ^0.0.2
2. Install it
You can install packages from the command line:
$ pub get
$ flutter pub get
Alternatively, your editor might support
pub get or
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Apr 4, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.7.1
- pana: 0.13.6
Health issues and suggestions
Document public APIs. (-1 points)
15 out of 15 API elements have no dartdoc comment.Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API.
The package description is too short. (-20 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
logart.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.