journify_flutter_plugin_moengage 1.0.0
journify_flutter_plugin_moengage: ^1.0.0 copied to clipboard
A Journify Flutter plugin for MoEngage
We analyzed this package 1 hour ago, and awarded it 110 pub points (of a possible 160):
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 50 to 180 characters to describe the package, what it does, and its target use case.
Homepage URL doesn't exist.
At the time of the analysis https://github.com/journify-io/journify-flutter#readme was unreachable. Make sure that the website is reachable via HEAD requests.
Repository URL doesn't exist.
At the time of the analysis https://github.com/journify-io/journify-flutter/tree/main/packages/plugins/plugin_moengage#readme 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/journify-io/journify-flutter/issues was unreachable. Make sure that the website is reachable via HEAD requests.
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
3 out of 25 API elements (12.0 %) 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: journify_flutter_plugin_moengage, journify_flutter_plugin_moengage.MoengageDestination, journify_flutter_plugin_moengage.MoengageDestination.MoengageDestination.new, journify_flutter_plugin_moengage.MoengageDestination.alias, journify_flutter_plugin_moengage.MoengageDestination.analytics.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add an example.
20/20 points: Supports 3 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
SDK issues found:
Package is not compatible with the Dart SDK.
Because:
journify_flutter_plugin_moengagethat depends on:moengage_flutterthat is a package requiring flutter.
-
✓ Android
-
✓ iOS
-
✓ Web
These platforms are not supported:
Package does not support platform `Windows`.
Because:
package:journify_flutter_plugin_moengage/journify_flutter_plugin_moengage.dartthat imports:package:journify_flutter_plugin_moengage/src/plugin_moengage_base.dartthat imports:package:moengage_flutter/moengage_flutter.dartthat declares support for platforms:Android,iOS,Web.
Package does not support platform `Linux`.
Because:
package:journify_flutter_plugin_moengage/journify_flutter_plugin_moengage.dartthat imports:package:journify_flutter_plugin_moengage/src/plugin_moengage_base.dartthat imports:package:moengage_flutter/moengage_flutter.dartthat declares support for platforms:Android,iOS,Web.
Package does not support platform `macOS`.
Because:
package:journify_flutter_plugin_moengage/journify_flutter_plugin_moengage.dartthat imports:package:journify_flutter_plugin_moengage/src/plugin_moengage_base.dartthat imports:package:moengage_flutter/moengage_flutter.dartthat declares support for platforms:Android,iOS,Web.
These issues are present but do not affect the score, because they may not originate in your package:
Package not compatible with platform Web
Because:
package:journify_flutter_plugin_moengage/journify_flutter_plugin_moengage.dartthat imports:package:journify_flutter_plugin_moengage/src/plugin_moengage_base.dartthat imports:package:moengage_flutter/moengage_flutter.dartthat imports:package:moengage_flutter_platform_interface/moengage_flutter_platform_interface.dartthat imports:package:moengage_flutter_platform_interface/src/utils/utils.dartthat imports:package:moengage_flutter_platform_interface/src/model/platforms.dartthat imports:dart:io
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:journify_flutter_plugin_moengage/journify_flutter_plugin_moengage.dartthat imports:package:journify_flutter_plugin_moengage/src/plugin_moengage_base.dartthat imports:package:moengage_flutter/moengage_flutter.dartthat imports:package:moengage_flutter_platform_interface/moengage_flutter_platform_interface.dartthat imports:package:moengage_flutter_platform_interface/src/utils/utils.dartthat imports:package:moengage_flutter_platform_interface/src/model/platforms.dartthat imports:dart:io
This package is not compatible with runtime wasm, and will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: 'setUniqueId' is deprecated and shouldn't be used. This method is deprecated in favour of identifyUser(). This method will be removed in 11.0.0.
lib/src/plugin_moengage_base.dart:17:31
╷
17 │ 'id': moEngageFlutter.setUniqueId,
│ ^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/plugin_moengage_base.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
journify_flutter |
^1.0.3 |
1.0.5 | 1.0.5 | |
moengage_flutter |
^9.1.1 |
9.2.1 | 10.4.0 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
app_set_id |
- | 1.3.0 | 1.3.0 | |
async |
- | 2.13.0 | 2.13.0 | |
characters |
- | 1.4.0 | 1.4.1 | |
clock |
- | 1.1.2 | 1.1.2 | |
code_assets |
- | 1.0.0 | 1.0.0 | |
collection |
- | 1.19.1 | 1.19.1 | |
crypto |
- | 3.0.7 | 3.0.7 | |
ffi |
- | 2.1.5 | 2.1.5 | |
file |
- | 7.0.1 | 7.0.1 | |
fixnum |
- | 1.1.1 | 1.1.1 | |
flutter_fgbg |
- | 0.7.1 | 0.7.1 | |
glob |
- | 2.1.3 | 2.1.3 | |
hooks |
- | 1.0.0 | 1.0.0 | |
http |
- | 1.6.0 | 1.6.0 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
intl |
- | 0.20.2 | 0.20.2 | |
json_annotation |
- | 4.10.0 | 4.10.0 | |
logger |
- | 2.6.2 | 2.6.2 | |
logging |
- | 1.3.0 | 1.3.0 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.17.0 | 1.18.1 | |
moengage_flutter_android |
- | 3.3.1 | 4.4.0 | |
moengage_flutter_ios |
- | 3.3.0 | 4.3.0 | |
moengage_flutter_platform_interface |
- | 3.2.0 | 4.0.1 | |
moengage_flutter_web |
- | 4.1.0 | 5.1.0 | |
native_toolchain_c |
- | 0.17.4 | 0.17.4 | |
objective_c |
- | 9.2.5 | 9.2.5 | |
path |
- | 1.9.1 | 1.9.1 | |
path_provider |
- | 2.1.5 | 2.1.5 | |
path_provider_android |
- | 2.2.22 | 2.2.22 | |
path_provider_foundation |
- | 2.6.0 | 2.6.0 | |
path_provider_linux |
- | 2.2.1 | 2.2.1 | |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 | |
path_provider_windows |
- | 2.3.0 | 2.3.0 | |
platform |
- | 3.1.6 | 3.1.6 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
pub_semver |
- | 2.2.0 | 2.2.0 | |
shared_preferences |
- | 2.5.4 | 2.5.4 | |
shared_preferences_android |
- | 2.4.20 | 2.4.20 | |
shared_preferences_foundation |
- | 2.5.6 | 2.5.6 | |
shared_preferences_linux |
- | 2.4.1 | 2.4.1 | |
shared_preferences_platform_interface |
- | 2.4.1 | 2.4.1 | |
shared_preferences_web |
- | 2.4.3 | 2.4.3 | |
shared_preferences_windows |
- | 2.4.1 | 2.4.1 | |
source_span |
- | 1.10.1 | 1.10.1 | |
state_notifier |
- | 0.7.2+1 | 1.0.0 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
uuid |
- | 4.5.2 | 4.5.2 | |
vector_math |
- | 2.2.0 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
xdg_directories |
- | 1.1.0 | 1.1.0 | |
yaml |
- | 3.1.3 | 3.1.3 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
The constraint `^9.1.1` on moengage_flutter does not support the stable version `10.0.0`.
Try running dart pub upgrade --major-versions moengage_flutter 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.8, Dart 3.10.8.
Check the analysis log for details.