flutter_blue_fork 0.8.2 flutter_blue_fork: ^0.8.2 copied to clipboard
Flutter plugin for connecting and communicating with Bluetooth Low Energy devices, on Android and iOS
We analyzed this package 18 days ago, and awarded it 140 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: BSD-3-Clause
.
10/10 points: 20% or more of the public API has dartdoc comments
1646 out of 2742 API elements (60.0 %) have documentation comments.
Some symbols that are missing documentation: flutter_blue
, flutter_blue.AdvertisementData
, flutter_blue.AdvertisementData.AdvertisementData.fromProto
, flutter_blue.AdvertisementData.connectable
, flutter_blue.AdvertisementData.localName
.
10/10 points: Package has an example
20/20 points: Supports 3 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ macOS
These platforms are not supported:
Package does not support platform `Windows`.
Because:
package:flutter_blue_fork/flutter_blue.dart
that declares support for platforms:Android
,iOS
,macOS
.
Package does not support platform `Linux`.
Because:
package:flutter_blue_fork/flutter_blue.dart
that declares support for platforms:Android
,iOS
,macOS
.
Package does not support platform `Web`.
Because:
package:flutter_blue_fork/flutter_blue.dart
that declares support for platforms:Android
,iOS
,macOS
.
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:flutter_blue_fork/flutter_blue.dart
that imports:dart:io
This package is not compatible with runtime wasm
, and will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
0/0 points: Swift Package Manager support
Package does not support the Swift Package Manager on macOS
It does not contain macos/flutter_blue_fork/Package.swift
.
This package for iOS or macOS does not support the Swift Package Manager. It will not receive full points in a future version of the scoring model.
See https://docs.flutter.dev/to/spm for details.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 19 issues. Showing the first 2:
INFO: The part-of directive uses a library name.
lib/src/advertising_mode.dart:2:1
╷
2 │ part of flutter_blue;
│ ^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/advertising_mode.dart
INFO: The part-of directive uses a library name.
lib/src/advertising_tx_power.dart:2:1
╷
2 │ part of flutter_blue;
│ ^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/advertising_tx_power.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
^1.15.0 |
1.19.0 | 1.19.1 |
convert |
^3.0.0 |
3.1.2 | 3.1.2 |
flutter |
flutter |
0.0.0 | 0.0.0 |
meta |
^1.3.0 |
1.15.0 | 1.16.0 |
protobuf |
^2.0.0 |
2.1.0 | 3.1.0 |
rxdart |
^0.27.7 |
0.27.7 | 0.28.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
characters |
- | 1.3.0 | 1.4.0 |
fixnum |
- | 1.1.1 | 1.1.1 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
sky_engine |
- | 0.0.0 | 0.0.0 |
typed_data |
- | 1.4.0 | 1.4.0 |
vector_math |
- | 2.1.4 | 2.1.4 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^2.0.0` on protobuf does not support the stable version `3.0.0`.
Try running dart pub upgrade --major-versions protobuf
to update the constraint.
The constraint `^0.27.7` on rxdart does not support the stable version `0.28.0`.
Try running dart pub upgrade --major-versions rxdart
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.