avo_inspector 1.0.0 avo_inspector: ^1.0.0 copied to clipboard
Avo Inspector for Dart. Find out what's wrong with your data. The first step to better analytics governance is knowing what's wrong with your data today.
We analyzed this package 3 days ago, and awarded it 130 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
.
0/10 points: 20% or more of the public API has dartdoc comments
1 out of 83 API elements (1.2 %) 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.
To highlight public API members missing documentation consider enabling the public_member_api_docs
lint.
Some symbols that are missing documentation: avo_batcher
, avo_batcher.AvoBatcher
, avo_batcher.AvoBatcher.AvoBatcher
, avo_batcher.AvoBatcher.avoInstallationId
, avo_batcher.AvoBatcher.batchFlushAttemptTimestamp
.
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.
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: Use 'isNotEmpty' instead of 'length' to test whether the collection is empty.
lib/avo_parser.dart:62:18
╷
62 │ } else if ((eventParam as Iterable).length > 0) {
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/avo_parser.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
flutter |
flutter |
0.0.0 | 0.0.0 |
http |
^0.13.4 |
0.13.6 | 1.2.2 |
shared_preferences |
^2.0.12 |
2.3.4 | 2.3.4 |
uuid |
^3.0.5 |
3.0.7 | 4.5.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.12.0 | 2.12.0 |
characters |
- | 1.3.0 | 1.4.0 |
collection |
- | 1.19.0 | 1.19.1 |
crypto |
- | 3.0.6 | 3.0.6 |
ffi |
- | 2.1.3 | 2.1.3 |
file |
- | 7.0.1 | 7.0.1 |
flutter_web_plugins |
- | 0.0.0 | 0.0.0 |
http_parser |
- | 4.1.1 | 4.1.1 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
meta |
- | 1.15.0 | 1.16.0 |
path |
- | 1.9.1 | 1.9.1 |
path_provider_linux |
- | 2.2.1 | 2.2.1 |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 |
path_provider_windows |
- | 2.3.0 | 2.3.0 |
platform |
- | 3.1.6 | 3.1.6 |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 |
shared_preferences_android |
- | 2.4.0 | 2.4.0 |
shared_preferences_foundation |
- | 2.5.4 | 2.5.4 |
shared_preferences_linux |
- | 2.4.1 | 2.4.1 |
shared_preferences_platform_interface |
- | 2.4.1 | 2.4.1 |
shared_preferences_web |
- | 2.4.2 | 2.4.2 |
shared_preferences_windows |
- | 2.4.1 | 2.4.1 |
sky_engine |
- | 0.0.0 | 0.0.0 |
source_span |
- | 1.10.1 | 1.10.1 |
string_scanner |
- | 1.4.1 | 1.4.1 |
term_glyph |
- | 1.2.2 | 1.2.2 |
typed_data |
- | 1.4.0 | 1.4.0 |
vector_math |
- | 2.1.4 | 2.1.4 |
web |
- | 1.1.0 | 1.1.0 |
xdg_directories |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^0.13.4` on http does not support the stable version `1.0.0`.
Try running dart pub upgrade --major-versions http
to update the constraint.
The constraint `^3.0.5` on uuid does not support the stable version `4.0.0`.
Try running dart pub upgrade --major-versions uuid
to update the constraint.
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.17
, Flutter 3.27.0
, Dart 3.6.0
.
Check the analysis log for details.