openworkflow_dart 0.1.0
openworkflow_dart: ^0.1.0 copied to clipboard
A workflow JSON Spec Parser for dart with service.
We analyzed this package 6 days ago, and awarded it 90 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.
0/10 points: 20% or more of the public API has dartdoc comments
2 out of 56 API elements (3.6 %) 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.
To highlight public API members missing documentation consider enabling the public_member_api_docs lint.
Some symbols that are missing documentation: openworkflow_dart.FunctionItem, openworkflow_dart.FunctionItem.FunctionItem.fromJson, openworkflow_dart.FunctionItem.FunctionItem.new, openworkflow_dart.FunctionItem.arguments, openworkflow_dart.FunctionItem.description.
10/10 points: Package has an example
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ Linux
-
✓ macOS
These platforms are not supported:
Package not compatible with platform Web
Because:
package:openworkflow_dart/openworkflow_dart.dartthat imports:package:openworkflow_dart/src/service/session.dartthat imports:package:opentool_dart/opentool_dart.dartthat imports:package:opentool_dart/src/opentool_loader.dartthat imports:dart:io
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 7 issues. Showing the first 2:
ERROR: No associated positional super constructor parameter.
lib/src/system_tools/system_driver.dart:5:22
╷
5 │ SystemDriver(super.openTool);
│ ^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/system_tools/system_driver.dart
INFO: The variable name 'FUNCTION_CALL' isn't a lowerCamelCase identifier.
lib/src/service/model.dart:2:17
╷
2 │ static String FUNCTION_CALL = "functionCall"; // FunctionCall
│ ^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/service/model.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
json_annotation |
^4.9.0 |
4.9.0 | 4.9.0 | |
opentool_dart |
^0.2.0 |
0.2.5 | 1.1.0 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
async |
- | 2.13.0 | 2.13.0 | |
collection |
- | 1.19.1 | 1.19.1 | |
dylib |
- | 0.3.3 | 0.3.3 | |
ffi |
- | 2.1.4 | 2.1.4 | |
http |
- | 1.6.0 | 1.6.0 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
json_rpc_2 |
- | 3.0.3 | 4.0.0 | |
libserialport |
- | 0.3.0+1 | 0.3.0+1 | |
logging |
- | 1.3.0 | 1.3.0 | |
meta |
- | 1.17.0 | 1.17.0 | |
modbus_client |
- | 1.4.4 | 1.4.4 | |
modbus_client_serial |
- | 1.3.1 | 1.3.1 | |
modbus_client_tcp |
- | 1.2.3 | 1.2.3 | |
modbus_client_udp |
- | 1.4.0 | 1.4.0 | |
openapi_dart |
- | 0.1.4 | 0.2.0 | |
openmodbus_dart |
- | 0.2.0 | 0.2.0 | Discontinued |
openrpc_dart |
- | 0.1.3 | 0.2.0 | |
path |
- | 1.9.1 | 1.9.1 | |
platform |
- | 3.1.6 | 3.1.6 | |
source_span |
- | 1.10.1 | 1.10.1 | |
stack_trace |
- | 1.12.1 | 1.12.1 | |
stream_channel |
- | 2.1.4 | 2.1.4 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
synchronized |
- | 3.4.0 | 3.4.0 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
web |
- | 1.1.1 | 1.1.1 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
The constraint `^0.2.0` on opentool_dart does not support the stable version `0.3.0`.
Try running dart pub upgrade --major-versions opentool_dart 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.23.3, Dart 3.10.4.
Check the analysis log for details.