v_chat_utils 0.8.0
v_chat_utils: ^0.8.0 copied to clipboard

Published 19 months ago • Latest: 1.0.1

discontinued

→

Metadata

utils for v chat sdk

More...

likes

30/ 160

pub points

popularity

We analyzed this package 2 days ago, and awarded it 30 pub points (of a possible 160):

Follow Dart file conventions

20 / 30

0/10 points: Provide a valid `pubspec.yaml`

The package description is too short.

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.

Repository URL doesn't exist.

At the time of the analysis https://github.com/hatemragab/v_chat_sdk/tree/master/core_packages/v_chat_utils was unreachable. Make sure that the website is reachable via HEAD requests.

Issue tracker URL doesn't exist.

At the time of the analysis https://github.com/hatemragab/v_chat_sdk/issues was unreachable. Make sure that the website is reachable via HEAD requests.

Failed to verify repository URL.

Please provide a valid repository URL in pubspec.yaml, such that:

repository can be cloned,
a clone of the repository contains a pubspec.yaml, which:,
- contains name: v_chat_utils,
- contains a version property, and,
- does not contain a publish_to property.

Repository has no matching pubspec.yaml with name: v_chat_utils.

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.

Provide documentation

0 / 20

0/10 points: 20% or more of the public API has dartdoc comments

Dependency resolution failed, unable to run dartdoc.

0/10 points: Package has an example

No example found.

See package layout guidelines on how to add an example.

Platform support

0 / 20

0/20 points: Platform support detection failed

Could not determine supported platforms as package resolution failed.

Run flutter pub get for more information.

0/0 points: WASM compatibility

Unable to detect compatibility with runtime wasm, and this package will not be rewarded full points in a future version of the scoring model.

See https://dart.dev/web/wasm for details.

Pass static analysis

0 / 50

0/50 points: code has no errors, warnings, lints, or formatting issues

Running flutter pub outdated failed with the following output:

Note: intl is pinned to version 0.19.0 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

Support up-to-date dependencies

10 / 40

0/10 points: All of the package dependencies are supported in the latest version

Could not run flutter pub outdated: flutter pub get failed:

OUT:
Resolving dependencies...
ERR:
Note: intl is pinned to version 0.19.0 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because v_chat_utils depends on flutter_localizations from sdk which depends on intl 0.19.0, intl 0.19.0 is required.
So, because v_chat_utils depends on intl ^0.17.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Try upgrading your constraint on intl: flutter pub add intl:^0.19.0

10/10 points: Package supports latest stable Dart and Flutter SDKs

0/20 points: Compatible with dependency constraint lower bounds

flutter pub downgrade failed with:

OUT:
Resolving dependencies...
ERR:
Note: intl is pinned to version 0.19.0 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because v_chat_utils depends on flutter_localizations from sdk which depends on intl 0.19.0, intl 0.19.0 is required.
So, because v_chat_utils depends on intl ^0.17.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Try upgrading your constraint on intl: flutter pub add intl:^0.19.0

Run flutter pub downgrade and then flutter 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.22.15, Flutter 3.24.5, Dart 3.5.4.

Check the analysis log for details.