FijkLog class

API for sending log output

Generally, you should use the FijkLog.d(msg), FijkLog.i(msg), FijkLog.w(msg), and FijkLog.e(msg) methods to write logs. You can then view the logs in console/logcat.

The order in terms of verbosity, from least to most is ERROR, WARN, INFO, DEBUG, VERBOSE. Verbose should always be skipped in an application except during development. Debug logs are compiled in but stripped at runtime. Error, warning and info logs are always kept.


hashCode int
The hash code for this object. [...]
read-only, inherited
runtimeType Type
A representation of the runtime type of the object.
read-only, inherited


noSuchMethod(Invocation invocation) → dynamic
Invoked when a non-existent method or property is accessed. [...]
toString() String
A string representation of this object. [...]


operator ==(Object other) bool
The equality operator. [...]

Static Methods

d(String msg, {String tag = 'fijk'}) → dynamic
log msg with FijkLogLevel.Debug level
e(String msg, {String tag = 'fijk'}) → dynamic
log msg with FijkLogLevel.Error level
i(String msg, {String tag = 'fijk'}) → dynamic
log msg with FijkLogLevel.Info level
log(FijkLogLevel level, String msg, String tag) → dynamic
log msg with level and tag to console
setLevel(FijkLogLevel level) → dynamic
Set global whole log level [...]
v(String msg, {String tag = 'fijk'}) → dynamic
log msg with FijkLogLevel.Verbose level
w(String msg, {String tag = 'fijk'}) → dynamic
log msg with FijkLogLevel.Warn level