morphable_shape 0.0.9
morphable_shape: ^0.0.9 copied to clipboard
A Flutter package for creating various shapes that are responsive and can morph betweem each other.
We analyzed this package 5 days ago, and awarded it 70 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
OUT: Documenting morphable_shape... Discovering libraries... ERR: dartdoc 8.3.3 (/tmp/analyzerMSNZYF/pub-cache/global_packages/dartdoc/bin/dartdoc.dart-3.7.2.snapshot) failed: fatal error: unable to locate the input directory at '/C:/Users/kevin/StudioProjects/[...] #0 PubPackageMeta.fromDir (package:dartdoc/src/package_meta.dart:215:7) #1 PubPackageMeta.fromFilename (package:dartdoc/src/package_meta.dart:202:27) #2 PackageMetaProvider.fromFilename (package:dartdoc/src/package_meta.dart:80:55) #3 PubPackageBuilder._packageMetasForFiles (package:dartdoc/src/model/package_builder.dart:204:32) #4 PubPackageBuilder._discoverLibraries (package:dartdoc/src/model/package_builder.dart:292:22)
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
Unable to detect compatibility with runtime wasm
, and this package will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 55 issues. Showing the first 2:
ERROR: A member named 'toJson' is defined in 'extension SystemMouseCursorsToJson on InvalidType' and 'extension ShapeSideExtension on ShapeSide', and neither is more specific.
lib/borderShapes/arc.dart:27:24
╷
27 │ rst["side"] = side.toJson();
│ ^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/borderShapes/arc.dart
ERROR: A member named 'toJson' is defined in 'extension SystemMouseCursorsToJson on InvalidType' and 'extension ShapeSideExtension on ShapeSide', and neither is more specific.
lib/borderShapes/arrow.dart:35:24
╷
35 │ rst["side"] = side.toJson();
│ ^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/borderShapes/arrow.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
flutter_class_parser |
^0.0.2 |
0.0.9 | 0.2.5 | |
length_unit |
^0.0.1 |
0.0.9 | 0.1.2 | Discontinued |
pedantic |
^1.9.0 |
1.11.1 | 1.11.1 | Discontinued |
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
.
Found 3 issues. Showing the first 2:
The constraint `^0.0.2` on flutter_class_parser does not support the stable version `0.1.0`.
Try running dart pub upgrade --major-versions flutter_class_parser
to update the constraint.
The constraint `^0.0.1` on length_unit does not support the stable version `0.1.0`.
Try running dart pub upgrade --major-versions length_unit
to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 1 error:
UNDEFINED_METHOD
-lib/morphable_shape_border.dart:130:23
- The method 'hashValues' isn't defined for the type 'MorphableShapeBorder'.
Run flutter pub downgrade
and then flutter analyze
to reproduce the above problem.
You may run dart pub upgrade --tighten
to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.22.20
, Flutter 3.29.2
, Dart 3.7.2
.
Check the analysis log for details.