micro_core_result 0.2.1 micro_core_result: ^0.2.1 copied to clipboard
This package is a simple approach to return multiple values, inspired on dartz package.
We analyzed this package 45 hours ago, and awarded it 160 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
Homepage URL doesn't exist.
At the time of the analysis https://www.jotapetecnologia.com.br/flutter/packages/micro_core_result
was unreachable. Make sure that the website is reachable via HEAD
requests.
Issue tracker URL doesn't exist.
At the time of the analysis https://github.com/JotaPe-Tecnologia/micro-core-result/issues
was unreachable. Make sure that the website is reachable via HEAD
requests.
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: Apache-2.0
.
10/10 points: 20% or more of the public API has dartdoc comments
5 out of 17 API elements (29.4 %) have documentation comments.
Some symbols that are missing documentation: micro_core_result
, micro_core_result.Left.call
, micro_core_result.Left.isLeft
, micro_core_result.Left.isRight
, micro_core_result.Left.l
.
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
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.
50/50 points: code has no errors, warnings, lints, or formatting issues
10/10 points: All of the package dependencies are supported in the latest version
No dependencies.
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
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade
does not expose any static analysis error.
Analyzed with Pana 0.22.17
, Dart 3.6.0
.
Check the analysis log for details.