firestore_paging_controller 0.1.0
firestore_paging_controller: ^0.1.0 copied to clipboard
Lazily load and display pages of items as the user scrolls down your screen, using Firestore with some enhancements.
We analyzed this package 16 hours ago, and awarded it 150 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
.
10/10 points: 20% or more of the public API has dartdoc comments
178 out of 209 API elements (85.2 %) have documentation comments.
Some symbols that are missing documentation: firestore_paging_controller
, firestore_paging_controller.CompletedListingBuilder
, firestore_paging_controller.ErrorListingBuilder
, firestore_paging_controller.FromMap
, firestore_paging_controller.ItemWidgetBuilder
.
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:firestore_paging_controller/firestore_paging_controller.dart
that imports:package:firestore_paging_controller/src/firestore_paging_controller.dart
that imports:package:firestore_paging_controller/src/data_cursor.dart
that imports:package:cloud_firestore/cloud_firestore.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.cn/web/wasm for details.
50/50 points: code has no errors, warnings, lints, or formatting issues
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
cloud_firestore |
^5.6.0 |
5.6.12 | 6.0.2 | |
infinite_scroll_pagination |
^4.1.0 |
4.1.0 | 5.1.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
_flutterfire_internals |
- | 1.3.59 | 1.3.62 | |
async |
- | 2.13.0 | 2.13.0 | |
boolean_selector |
- | 2.1.2 | 2.1.2 | |
characters |
- | 1.4.0 | 1.4.1 | |
clock |
- | 1.1.2 | 1.1.2 | |
cloud_firestore_platform_interface |
- | 6.6.12 | 7.0.2 | |
cloud_firestore_web |
- | 4.4.12 | 5.0.2 | |
collection |
- | 1.19.1 | 1.19.1 | |
fake_async |
- | 1.3.3 | 1.3.3 | |
firebase_core |
- | 3.15.2 | 4.1.1 | |
firebase_core_platform_interface |
- | 6.0.1 | 6.0.1 | |
firebase_core_web |
- | 2.24.1 | 3.1.1 | |
flutter_staggered_grid_view |
- | 0.7.0 | 0.7.0 | |
leak_tracker |
- | 11.0.2 | 11.0.2 | |
leak_tracker_flutter_testing |
- | 3.0.10 | 3.0.10 | |
leak_tracker_testing |
- | 3.0.2 | 3.0.2 | |
matcher |
- | 0.12.17 | 0.12.17 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.16.0 | 1.17.0 | |
path |
- | 1.9.1 | 1.9.1 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
sliver_tools |
- | 0.2.12 | 0.2.12 | |
source_span |
- | 1.10.1 | 1.10.1 | |
stack_trace |
- | 1.12.1 | 1.12.1 | |
stream_channel |
- | 2.1.4 | 2.1.4 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
test_api |
- | 0.7.6 | 0.7.7 | |
vector_math |
- | 2.2.0 | 2.2.0 | |
vm_service |
- | 15.0.2 | 15.0.2 | |
web |
- | 1.1.1 | 1.1.1 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^5.6.0` on cloud_firestore does not support the stable version `6.0.0`.
Try running dart pub upgrade --major-versions cloud_firestore
to update the constraint.
The constraint `^4.1.0` on infinite_scroll_pagination does not support the stable version `5.0.0`.
Try running dart pub upgrade --major-versions infinite_scroll_pagination
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.23
, Flutter 3.35.5
, Dart 3.9.2
.
Check the analysis log for details.