brick_graphql 2.0.2
brick_graphql: ^2.0.2 copied to clipboard
GraphQL connector for Brick, a data persistence library. Includes annotations, adapter, model, and provider.
We analyzed this package 28 hours ago, and awarded it 140 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
48 out of 64 API elements (75.0 %) have documentation comments.
Some symbols that are missing documentation: graphql
, graphql.GraphqlAdapter.GraphqlAdapter.new
, graphql.GraphqlAdapter.fieldsToGraphqlRuntimeDefinition
, graphql.GraphqlAdapter.fromGraphql
, graphql.GraphqlAdapter.queryOperationTransformer
.
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.cn/web/wasm for details.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 12 issues. Showing the first 2:
INFO: 'providerArgs' is deprecated and shouldn't be used. Use limit, offset, limitBy, orderBy, or forProviders instead.
lib/src/graphql_request.dart:44:23
╷
44 │ context: query?.providerArgs['context'] != null
│ ^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/graphql_request.dart
INFO: 'providerArgs' is deprecated and shouldn't be used. Use limit, offset, limitBy, orderBy, or forProviders instead.
lib/src/graphql_request.dart:45:67
╷
45 │ ? Context.fromMap(Map<String, ContextEntry>.from(query?.providerArgs['context'])
│ ^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/graphql_request.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
brick_core |
^1.1.1 |
1.4.0 | 2.0.0 | |
collection |
>=1.15.0 <2.0.0 |
1.19.1 | 1.19.1 | |
gql |
>=0.13.0 <1.0.0 |
0.14.0 | 1.0.1 | |
gql_exec |
>=0.3.0 <1.0.0 |
0.4.3 | 1.0.0+1 | |
gql_link |
>=0.4.0 <1.0.0 |
0.5.1 | 1.1.0 | |
logging |
>=1.0.0 <2.0.0 |
1.3.0 | 1.3.0 | |
meta |
>=1.3.0 <2.0.0 |
1.17.0 | 1.17.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
path |
- | 1.9.1 | 1.9.1 | |
source_span |
- | 1.10.1 | 1.10.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
Found 4 issues. Showing the first 2:
The constraint `^1.1.1` on brick_core does not support the stable version `2.0.0`.
Try running dart pub upgrade --major-versions brick_core
to update the constraint.
The constraint `>=0.13.0 <1.0.0` on gql does not support the stable version `1.0.0`.
Try running dart pub upgrade --major-versions gql
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
, Dart 3.9.3
.
Check the analysis log for details.