telegram_crash_log 0.0.1
telegram_crash_log: ^0.0.1 copied to clipboard
Send telegram error logs to telegram channel
We analyzed this package 3 days ago, and awarded it 100 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.
-
pubspec.yamldoesn't have ahomepageentry. -
pubspec.yamldoesn't have arepositoryentry.
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
1 out of 4 API elements (25.0 %) have documentation comments.
Some symbols that are missing documentation: telegram_crash_log, telegram_crash_log.TelegramCrashLog.TelegramCrashLog.new, telegram_crash_log.TelegramCrashLog.logError.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add 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 does not support platform `Web`.
Because:
package:telegram_crash_log/telegram_crash_log.dartthat imports:package:path_provider/path_provider.dartthat declares support for platforms:Android,iOS,Windows,Linux,macOS.
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:telegram_crash_log/telegram_crash_log.dartthat imports:package:package_info_plus/package_info_plus.dartthat imports:package:package_info_plus/src/package_info_plus_windows.dartthat imports:package:package_info_plus/src/file_version_info.dartthat imports:package:win32/win32.dartthat declares support for platforms:Windows.
Package does not support platform `iOS`.
Because:
package:telegram_crash_log/telegram_crash_log.dartthat imports:package:package_info_plus/package_info_plus.dartthat imports:package:package_info_plus/src/package_info_plus_windows.dartthat imports:package:package_info_plus/src/file_version_info.dartthat imports:package:win32/win32.dartthat declares support for platforms:Windows.
Package does not support platform `Linux`.
Because:
package:telegram_crash_log/telegram_crash_log.dartthat imports:package:package_info_plus/package_info_plus.dartthat imports:package:package_info_plus/src/package_info_plus_windows.dartthat imports:package:package_info_plus/src/file_version_info.dartthat imports:package:win32/win32.dartthat declares support for platforms:Windows.
Package does not support platform `macOS`.
Because:
package:telegram_crash_log/telegram_crash_log.dartthat imports:package:package_info_plus/package_info_plus.dartthat imports:package:package_info_plus/src/package_info_plus_windows.dartthat imports:package:package_info_plus/src/file_version_info.dartthat imports:package:win32/win32.dartthat declares support for platforms:Windows.
30/50 points: code has no errors, warnings, lints, or formatting issues
WARNING: The value of the local variable 'response' isn't used.
lib/telegram_crash_log.dart:29:13
╷
29 │ final response = await bot.sendDocument(ChatID(-1001845381104),
│ ^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/telegram_crash_log.dart
INFO: Missing type annotation.
lib/telegram_crash_log.dart:11:10
╷
11 │ static logError(FlutterErrorDetails detail, String token, int chatID,{String info = ''}) async {
│ ^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/telegram_crash_log.dart
10/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
dart_telegram_bot |
^1.0.0 |
1.0.0 | 1.0.0 | |
package_info_plus |
any |
9.0.0 | 9.0.0 | |
path_provider |
^2.0.11 |
2.1.5 | 2.1.5 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
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.2.0 | 2.2.0 | |
file |
- | 7.0.1 | 7.0.1 | |
glob |
- | 2.1.3 | 2.1.3 | |
hooks |
- | 1.0.1 | 1.0.1 | |
http |
- | 0.13.6 | 1.6.0 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
logging |
- | 1.3.0 | 1.3.0 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.17.0 | 1.18.1 | |
native_toolchain_c |
- | 0.17.4 | 0.17.4 | |
objective_c |
- | 9.3.0 | 9.3.0 | |
package_info_plus_platform_interface |
- | 3.2.1 | 3.2.1 | |
path |
- | 1.9.1 | 1.9.1 | |
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 | |
source_span |
- | 1.10.2 | 1.10.2 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
vector_math |
- | 2.2.0 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
win32 |
- | 5.15.0 | 5.15.0 | |
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.
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 1 error:
UNDEFINED_GETTER-lib/telegram_crash_log.dart:23:50- The getter 'buildSignature' isn't defined for the type 'PackageInfo'.
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.23.9, Flutter 3.38.9, Dart 3.10.8.
Check the analysis log for details.