ncmb 2.7.0
ncmb: ^2.7.0 copied to clipboard
Dart and Flutter library for Nifcloud mobile backend(NCMB). Nifcloud mobile backend is a web service of mBaaS.
We analyzed this package 43 hours ago, and awarded it 130 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
162 out of 167 API elements (97.0 %) have documentation comments.
Some symbols that are missing documentation: ncmb
, ncmb.NCMBFile.contents
, ncmb.NCMBQuery.allInArray
, ncmb.NCMBRelation.NCMBRelation.new
, ncmb.NCMBRequest.NCMBRequest.new
.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add 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
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.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 11 issues. Showing the first 2:
INFO: An uninitialized field should have an explicit type annotation.
lib/src/file.dart:14:7
╷
14 │ var data;
│ ^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/file.dart
INFO: Use 'isEmpty' instead of 'length' to test whether the collection is empty.
lib/src/file.dart:93:12
╷
93 │ return res.keys.length == 0;
│ ^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/file.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
crypto |
^3.0.2 |
3.0.6 | 3.0.6 | |
dio |
^4.0.3 |
4.0.6 | 5.8.0+1 | |
http_parser |
^4.0.0 |
4.1.2 | 4.1.2 | |
intl |
^0.17.0 |
0.17.0 | 0.20.2 | |
mime |
^1.0.1 |
1.0.6 | 2.0.0 | |
package_info |
^2.0.2 |
2.0.2 | 2.0.2 | Discontinued |
shared_preferences |
^2.0.9 |
2.5.3 | 2.5.3 | |
uuid |
^3.0.5 |
3.0.7 | 4.5.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
characters |
- | 1.4.0 | 1.4.1 | |
clock |
- | 1.1.2 | 1.1.2 | |
collection |
- | 1.19.1 | 1.19.1 | |
ffi |
- | 2.1.4 | 2.1.4 | |
file |
- | 7.0.1 | 7.0.1 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.16.0 | 1.17.0 | |
path |
- | 1.9.1 | 1.9.1 | |
path_provider_linux |
- | 2.2.1 | 2.2.1 | |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 | |
path_provider_windows |
- | 2.3.0 | 2.3.0 | |
platform |
- | 3.1.6 | 3.1.6 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
shared_preferences_android |
- | 2.4.10 | 2.4.10 | |
shared_preferences_foundation |
- | 2.5.4 | 2.5.4 | |
shared_preferences_linux |
- | 2.4.1 | 2.4.1 | |
shared_preferences_platform_interface |
- | 2.4.1 | 2.4.1 | |
shared_preferences_web |
- | 2.4.3 | 2.4.3 | |
shared_preferences_windows |
- | 2.4.1 | 2.4.1 | |
source_span |
- | 1.10.1 | 1.10.1 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
vector_math |
- | 2.1.4 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
xdg_directories |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
Found 5 issues. Showing the first 2:
The constraint `^4.0.3` on dio does not support the stable version `5.0.0`.
Try running dart pub upgrade --major-versions dio
to update the constraint.
The constraint `^0.17.0` on intl does not support the stable version `0.18.0`.
Try running dart pub upgrade --major-versions intl
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.21
, Dart 3.8.1
.
Check the analysis log for details.