navigation_builder 0.0.3 navigation_builder: ^0.0.3 copied to clipboard
A Flutter Navigation 2 with the ease of Navigation 1.
We analyzed this package 2 days ago, and awarded it 80 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
The package description is too short.
Add more detail to the description
field of pubspec.yaml
. Use 60 to 180 characters to describe the package, what it does, and its target use case.
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
74 out of 107 API elements (69.2 %) have documentation comments.
Some symbols that are missing documentation: navigation_builder
, navigation_builder.MaterialPageArgument
, navigation_builder.MaterialPageArgument.MaterialPageArgument
, navigation_builder.MaterialPageArgument.arguments
, navigation_builder.MaterialPageArgument.child
.
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 15 issues. Showing the first 2:
ERROR: The type 'PersistentBottomSheetController' is declared with 0 type parameters, but 1 type arguments were given.
lib/src/rm_scaffold.dart:102:3
╷
102 │ PersistentBottomSheetController<T> showBottomSheet<T>(
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/rm_scaffold.dart
ERROR: The method 'PersistentBottomSheetController Function(WidgetBuilder, {Color? backgroundColor, Clip? clipBehavior, BoxConstraints? constraints, double? elevation, bool? enableDrag, ShapeBorder? shape, AnimationStyle? sheetAnimationStyle, bool? showDragHandle, AnimationController? transitionAnimationController})' is declared with 0 type parameters, but 1 type arguments are given.
lib/src/rm_scaffold.dart:124:44
╷
124 │ final r = scaffoldState.showBottomSheet<T>(
│ ^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/rm_scaffold.dart
10/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 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
characters |
- | 1.3.0 | 1.3.1 |
collection |
- | 1.18.0 | 1.19.1 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
meta |
- | 1.15.0 | 1.16.0 |
sky_engine |
- | 0.0.99 | 0.0.99 |
vector_math |
- | 2.1.4 | 2.1.4 |
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
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 2 errors:
WRONG_NUMBER_OF_TYPE_ARGUMENTS
-lib/src/rm_scaffold.dart:102:3
- The type 'PersistentBottomSheetController' is declared with 0 type parameters, but 1 type arguments were given.WRONG_NUMBER_OF_TYPE_ARGUMENTS_METHOD
-lib/src/rm_scaffold.dart:124:44
- The method 'PersistentBottomSheetController Function(WidgetBuilder, {Color? backgroundColor, Clip? clipBehavior, BoxConstraints? constraints, double? elevation, bool? enableDrag, ShapeBorder? shape, AnimationStyle? sheetAnimationStyle, bool? showDragHandle, AnimationController? transitionAnimationController})' is declared with 0 type parameters, but 1 type arguments are given.
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.15
, Flutter 3.24.4
, Dart 3.5.4
.
Check the analysis log for details.