print_remover 1.0.1
print_remover: ^1.0.1 copied to clipboard
print_remover pacakges will help you delete all the print statement from your code.
We analyzed this package 23 days ago, and awarded it 135 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
5/5 points: Provide a valid README.md
0/5 points: Provide a valid CHANGELOG.md
`CHANGELOG.md` does not contain reference to the current version ("1.0.1").
Changelog entries help developers follow the progress of your package. Check out the Dart conventions for Maintaining a package changelog.
10/10 points: Use an OSI-approved license
Detected license: MIT.
10/10 points: 20% or more of the public API has dartdoc comments
2 out of 4 API elements (50.0 %) have documentation comments.
Some symbols that are missing documentation: print_remover.PrintRemover.PrintRemover.new, print_remover.PrintRemover.start.
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 not compatible with platform Web
Because:
package:print_remover/print_remover.dartthat imports:package:print_remover/src/print_remover_base.dartthat imports:dart:io
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: Missing type annotation.
lib/src/print_remover_base.dart:5:3
╷
5 │ start() async {
│ ^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/print_remover_base.dart
10/10 points: All of the package dependencies are supported in the latest version
No 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
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade does not expose any static analysis error.
Analyzed with Pana 0.23.3, Dart 3.10.4.
Check the analysis log for details.