radio_group_v2 1.0.2
radio_group_v2: ^1.0.2 copied to clipboard
A widget that groups radio buttons so they can work together to give the user a pleasant experience when making selections within the app.
We analyzed this package 4 days ago, and awarded it 140 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
Failed to verify repository URL.
Please provide a valid repository
URL in pubspec.yaml
, such that:
repository
can be cloned,- a clone of the repository contains a
pubspec.yaml
, which:,- contains
name: radio_group_v2
, - contains a
version
property, and, - does not contain a
publish_to
property.
- contains
Repository has no matching pubspec.yaml
with name: radio_group_v2
.
Homepage URL doesn't exist.
At the time of the analysis https://github.com/babincc/flutter_workshop/tree/master/plugins/radio_group_v2
was unreachable. Make sure that the website is reachable via HEAD
requests.
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
34 out of 39 API elements (87.2 %) have documentation comments.
Some symbols that are missing documentation: radio_group_v2
, radio_group_v2.RadioGroupController.RadioGroupController.new
, radio_group_v2_web
, radio_group_v2_web.RadioGroupV2Web.RadioGroupV2Web.new
, radio_group_v2_web.RadioGroupV2Web.registerWith
.
10/10 points: Package has an example
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ macOS
-
✓ Web
These platforms are not supported:
Package does not support platform `Linux`.
Because:
package:radio_group_v2/radio_group_v2.dart
that declares support for platforms:Android
,iOS
,Windows
,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.
0/0 points: Swift Package Manager support
Package does not support the Swift Package Manager on macOS
It does not contain macos/radio_group_v2/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 3 issues. Showing the first 2:
INFO: 'MaterialStateProperty' is deprecated and shouldn't be used. Use WidgetStateProperty instead. Moved to the Widgets layer to make code available outside of Material. This feature was deprecated after v3.19.0-0.3.pre.
lib/radio_group_v2.dart:458:9
╷
458 │ final MaterialStateProperty<Color?>? fillColor;
│ ^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/radio_group_v2.dart
INFO: 'MaterialStateProperty' is deprecated and shouldn't be used. Use WidgetStateProperty instead. Moved to the Widgets layer to make code available outside of Material. This feature was deprecated after v3.19.0-0.3.pre.
lib/radio_group_v2.dart:504:9
╷
504 │ final MaterialStateProperty<Color?>? overlayColor;
│ ^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/radio_group_v2.dart
10/10 points: All of the package dependencies are supported in the latest version
No dependencies.
Transitive dependencies
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
characters |
- | 1.4.0 | 1.4.0 | |
collection |
- | 1.19.1 | 1.19.1 | |
material_color_utilities |
- | 0.11.1 | 0.12.0 | |
meta |
- | 1.16.0 | 1.16.0 | |
vector_math |
- | 2.1.4 | 2.1.5 |
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.20
, Flutter 3.29.2
, Dart 3.7.2
.
Check the analysis log for details.