angel3_migration 8.1.1 angel3_migration: ^8.1.1 copied to clipboard
Database migration runtime for Angel3 ORM. Use this package to define schemas.
We analyzed this package 8 days ago, and awarded it 130 pub points (of a possible 140):
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: BSD-3-Clause
.
0/10 points: 20% or more of the public API has dartdoc comments
11 out of 63 API elements (17.5 %) have documentation comments.
Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API. Document at least 20% of the public API elements.
Some symbols that are missing documentation: angel3_migration
, angel3_migration.Migration
, angel3_migration.Migration.Migration
, angel3_migration.Migration.down
, angel3_migration.Migration.up
.
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
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
Package | Constraint | Compatible | Latest |
---|---|---|---|
angel3_orm |
^8.0.0 |
8.1.1 | 8.1.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
charcode |
- | 1.3.1 | 1.3.1 |
clock |
- | 1.1.1 | 1.1.1 |
collection |
- | 1.18.0 | 1.18.0 |
intl |
- | 0.19.0 | 0.19.0 |
logging |
- | 1.2.0 | 1.2.0 |
meta |
- | 1.14.0 | 1.14.0 |
optional |
- | 6.1.0+1 | 6.1.0+1 |
path |
- | 1.9.0 | 1.9.0 |
source_span |
- | 1.10.0 | 1.10.0 |
string_scanner |
- | 1.2.0 | 1.2.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
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
Analyzed with Pana 0.22.3
, Dart 3.3.3
.
Check the analysis log for details.