widgetbook2 2.4.2 widgetbook2: ^2.4.2 copied to clipboard
A flutter storybook that helps professionals and teams to catalogue their widgets.
We analyzed this package 3 days ago, and awarded it 70 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: widgetbook2
, - contains a
version
property, and, - does not contain a
publish_to
property.
- contains
Repository has no matching pubspec.yaml
with name: widgetbook2
.
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
201 out of 422 API elements (47.6 %) have documentation comments.
Some symbols that are missing documentation: widgetbook2
, widgetbook2.AppBuilderFunction
, widgetbook2.AppInfo
, widgetbook2.AppInfo.AppInfo
, widgetbook2.Device.copyWith
.
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 23 issues. Showing the first 2:
ERROR: The name 'SearchBar' is defined in the libraries 'package:flutter/src/material/search_anchor.dart (via package:flutter/material.dart)' and 'package:widgetbook2/src/widgets/search_bar.dart'.
lib/src/navigation/navigation_panel.dart:49:17
╷
49 │ const SearchBar(),
│ ^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/navigation/navigation_panel.dart
WARNING: The parameter type of '==' operators should be non-nullable.
lib/src/devices/devices_state.freezed.dart:107:17
╷
107 │ bool operator ==(dynamic other) {
│ ^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/devices/devices_state.freezed.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 |
device_frame |
^1.1.0 |
1.2.0 | 1.2.0 |
flutter |
flutter |
0.0.0 | 0.0.0 |
freezed_annotation |
^2.2.0 |
2.4.4 | 2.4.4 |
go_router |
^6.2.0 |
6.5.9 | 14.6.2 |
meta |
^1.8.0 |
1.15.0 | 1.16.0 |
nested |
^1.0.0 |
1.0.0 | 1.0.0 |
provider |
^6.0.5 |
6.1.2 | 6.1.2 |
widgetbook_models |
^0.0.7 |
0.0.7 | 0.0.7 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
characters |
- | 1.3.0 | 1.4.0 |
flutter_web_plugins |
- | 0.0.0 | 0.0.0 |
json_annotation |
- | 4.9.0 | 4.9.0 |
logging |
- | 1.3.0 | 1.3.0 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
sky_engine |
- | 0.0.0 | 0.0.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 `^6.2.0` on go_router does not support the stable version `7.0.0`.
Try running dart pub upgrade --major-versions go_router
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:
AMBIGUOUS_IMPORT
-lib/src/navigation/navigation_panel.dart:49:17
- The name 'SearchBar' is defined in the libraries 'package:flutter/src/material/search_anchor.dart (via package:flutter/material.dart)' and 'package:widgetbook2/src/widgets/search_bar.dart'.
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.17
, Flutter 3.27.0
, Dart 3.6.0
.
Check the analysis log for details.