mbautomation 2.1.1 mbautomation: ^2.1.1 copied to clipboard
MBAutomation plugin for MBurger that lets you present push and in app messages based on the behavior of the user.
We analyzed this package 28 hours ago, and awarded it 130 pub points (of a possible 140):
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
171 out of 198 API elements (86.4 %) have documentation comments.
Some symbols that are missing documentation: mb_app_opening_trigger
, mb_app_opening_trigger.MBAppOpeningTrigger.MBAppOpeningTrigger.fromJsonDictionary
, mb_automation_database
, mb_automation_event
, mb_automation_messages_manager
.
10/10 points: Package has an example
20/20 points: Supports 2 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
- ✓ Android
- ✓ iOS
These platforms are not supported:
Package does not support platform `Windows`.
Because:
package:mbautomation/mbautomation.dart
that declares support for platforms:Android
,iOS
.
Package does not support platform `Linux`.
Because:
package:mbautomation/mbautomation.dart
that declares support for platforms:Android
,iOS
.
Package does not support platform `macOS`.
Because:
package:mbautomation/mbautomation.dart
that declares support for platforms:Android
,iOS
.
Package does not support platform `Web`.
Because:
package:mbautomation/mbautomation.dart
that declares support for platforms:Android
,iOS
.
These issues are present but do not affect the score, because they may not originate in your package:
Package does not support platform `Android`.
Because:
package:mbautomation/mbautomation.dart
that imports:package:mbautomation/mbautomation_plugin.dart
that imports:package:mbmessages/push_notifications/mbpush.dart
that imports:package:mpush/mpush.dart
that imports:package:mpush/mpush_api.dart
that imports:package:device_info_plus/device_info_plus.dart
that imports:package:device_info_plus/src/device_info_plus_windows.dart
that imports:package:win32_registry/win32_registry.dart
that declares support for platforms:Windows
.
Package does not support platform `iOS`.
Because:
package:mbautomation/mbautomation.dart
that imports:package:mbautomation/mbautomation_plugin.dart
that imports:package:mbmessages/push_notifications/mbpush.dart
that imports:package:mpush/mpush.dart
that imports:package:mpush/mpush_api.dart
that imports:package:device_info_plus/device_info_plus.dart
that imports:package:device_info_plus/src/device_info_plus_windows.dart
that imports:package:win32_registry/win32_registry.dart
that declares support for platforms:Windows
.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 7 issues. Showing the first 2:
INFO: The argument type 'int' isn't related to 'String'.
lib/triggers/managers/mb_automation_push_notifications_manager.dart:158:48
╷
158 │ int messageShowCount = showedMessagesCount[message.id] ?? 0;
│ ^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/triggers/managers/mb_automation_push_notifications_manager.dart
lib/triggers/managers/mb_automation_messages_manager.dart doesn't match the Dart formatter.
To format your files run: dart format .
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
^1.16.0 |
1.18.0 | 1.18.0 |
flutter |
flutter |
0.0.0 | 0.0.0 |
http |
^1.1.0 |
1.2.1 | 1.2.1 |
mbaudience |
^2.1.1 |
2.1.1+1 | 2.1.1+1 |
mbmessages |
^2.1.1 |
2.1.2 | 2.1.2 |
mburger |
^2.1.1 |
2.1.1 | 2.1.1 |
path |
^1.8.3 |
1.9.0 | 1.9.0 |
path_provider |
^2.0.15 |
2.1.3 | 2.1.3 |
shared_preferences |
^2.2.0 |
2.2.3 | 2.2.3 |
sqflite |
^2.3.0 |
2.3.3 | 2.3.3 |
Transitive dependencies
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Flutter 3.19.5
, Dart 3.3.3
.
Check the analysis log for details.