filterable_logger 0.0.7 filterable_logger: ^0.0.7 copied to clipboard
A logger with color output and filters.
We analyzed this package 16 hours ago, and awarded it 110 pub points (of a possible 140):
0/10 points: Provide a valid pubspec.yaml
The package description is too short.
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.
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: MIT
.
0/10 points: 20% or more of the public API has dartdoc comments
2 out of 31 API elements (6.5 %) have documentation comments.
Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API. Document at least 20% of the public API elements.
Some symbols that are missing documentation: filterable_logger
, filterable_logger.FilterableLogger
, filterable_logger.FilterableLogger.FilterableLogger
, filterable_logger.FilterableLogger.config
, filterable_logger.FilterableLogger.currentLogLevel
.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add an example.
20/20 points: Supports 6 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
- ✓ Android
- ✓ iOS
- ✓ Windows
- ✓ Linux
- ✓ macOS
- ✓ Web
50/50 points: code has no errors, warnings, lints, or formatting issues
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
logging |
>=1.0.0 <2.0.0 |
1.2.0 | 1.2.0 |
stack_trace |
>=1.0.0 <2.0.0 |
1.11.1 | 1.11.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
path |
- | 1.9.0 | 1.9.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.4
.
Check the analysis log for details.