olos_sdk 1.0.600
olos_sdk: ^1.0.600 copied to clipboard
Designed for Dart apps, this middleware links with Olos API. Beyond standard connections, it enables WebSocket for seamless event reception via Olos Easy Connection.
1
likes
50/ 160
pub points
80
downloads
We analyzed this package 17 hours ago, and awarded it 50 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
Dependency resolution failed, unable to run dartdoc.
10/10 points: Package has an example
0/20 points: Platform support detection failed
Could not determine supported platforms as package resolution failed.
Run dart pub get for more information.
0/50 points: code has no errors, warnings, lints, or formatting issues
- Running
dart pub outdatedfailed with the following output:
Exceeded timeout of 0:02:00.000000
0/10 points: All of the package dependencies are supported in the latest version
- Could not run
dart pub outdated:dart pub getfailed:
OUT:
Resolving dependencies...
Downloading packages...
+ _fe_analyzer_shared 99.0.0
+ analyzer 12.1.0
+ any_base 2.0.0
+ args 2.7.0
+ async 2.13.1
+ boolean_selector 2.1.2
+ build 4.0.5
+ build_config 1.3.0
[66 more lines]
ERR:
Exceeded timeout of 0:02:00.000000
10/10 points: Package supports latest stable Dart and Flutter SDKs
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 2 errors:
URI_DOES_NOT_EXIST-lib/main.dart:17:8- Target of URI doesn't exist: 'src/ws/olos_agent_ws.dart'.NOT_ENOUGH_POSITIONAL_ARGUMENTS-lib/olos_test.dart:41:29- 3 positional arguments expected by 'createOlos', but 1 found.
Run dart pub downgrade and then dart analyze to reproduce the above problem.
You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.23.12, Dart 3.11.2.
Check the analysis log for details.