Brick SQLite Abstract #
Adding class- and field-level configuration to the SQLite provider.
Why isn't this package part of brick_sqlite?
dart:mirrors to determine field types and class makeup. Flutter cannot use
dart:mirrors. brick_sqlite relies on Flutter. Therefore, to use annotations for SQLite (annotations provide serdes information in generated code), this package has to be separated so that brick_build does not import brick_sqlite.
- Use single quotes when generating
Migration#versionto comply with default analyzer options
- Fix linter hints
- SqliteModel moved to this package from
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: brick_sqlite_abstract: ^0.0.2
2. Install it
You can install packages from the command line:
$ pub get
$ flutter pub get
Alternatively, your editor might support
pub get or
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
import 'package:brick_sqlite_abstract/annotations.dart'; import 'package:brick_sqlite_abstract/db.dart'; import 'package:brick_sqlite_abstract/sqlite_model.dart';
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Jan 19, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.7.0
- pana: 0.13.4
lib/src/db/migration_commands/insert_column.dart. (-0.50 points)
lib/src/db/migration_commands/insert_column.dart reported 1 hint:
line 89 col 40: Avoid const keyword.
dartfmt to format
dartfmt to format
Fix additional 6 files with analysis or formatting issues.
Additional issues in the following files:
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
brick_sqlite_abstract.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.
The package description is too short. (-1 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.