pretty_dio_logger 1.4.0 pretty_dio_logger: ^1.4.0 copied to clipboard
Pretty Dio logger is a Dio interceptor that logs network calls in a pretty, easy to read format.
We analyzed this package 40 hours ago, and awarded it 160 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
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
.
10/10 points: 20% or more of the public API has dartdoc comments
28 out of 29 API elements (96.6 %) have documentation comments.
Some symbols that are missing documentation: pretty_dio_logger
.
10/10 points: Package has an example
20/20 points: Supports 6 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ Linux
-
✓ macOS
-
✓ Web
0/0 points: WASM compatibility
This package is compatible with runtime wasm
, and will be rewarded additional points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
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 |
---|---|---|---|
dio |
^5.5.0 |
5.7.0 | 5.7.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.12.0 | 2.12.0 |
collection |
- | 1.19.1 | 1.19.1 |
dio_web_adapter |
- | 2.0.0 | 2.0.0 |
http_parser |
- | 4.1.1 | 4.1.1 |
meta |
- | 1.16.0 | 1.16.0 |
path |
- | 1.9.1 | 1.9.1 |
source_span |
- | 1.10.0 | 1.10.0 |
string_scanner |
- | 1.4.0 | 1.4.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.4.0 | 1.4.0 |
web |
- | 1.1.0 | 1.1.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
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade
does not expose any static analysis error.
Analyzed with Pana 0.22.15
, Dart 3.5.4
.
Check the analysis log for details.