Flutter plugin for umeng:analytics
import 'package:umeng_analytics/umeng_analytics.dart'; UMengAnalytics.init('AppKey', channel: 'default', policy: Policy.BATCH, encrypt: true, reportCrash: false);
- update some document.
- initial release. only init.
Demonstrates how to use the umeng_analytics plugin.
Getting Started #
This project is a starting point for a Flutter application.
A few resources to get you started if this is your first Flutter project:
For help getting started with Flutter, view our online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: umeng_analytics: ^0.0.6
2. Install it
You can install packages from the command line:
$ flutter pub get
Alternatively, your editor might support
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Jan 21, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.7.0
- pana: 0.13.4
- Flutter: 1.12.13+hotfix.5
Health issues and suggestions
Document public APIs. (-1 points)
12 out of 12 API elements have no dartdoc comment.Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API.
lib/umeng_analytics.dart. (-1.99 points)
lib/umeng_analytics.dart reported 4 hints:
line 6 col 20: Name non-constant identifiers using lowerCamelCase.
line 7 col 20: Name non-constant identifiers using lowerCamelCase.
line 8 col 20: Name non-constant identifiers using lowerCamelCase.
line 9 col 20: Name non-constant identifiers using lowerCamelCase.
Maintenance issues and suggestions
The description contains too many non-ASCII characters. (-20 points)
The site uses English as its primary language. The value of the
description field in your package's
pubspec.yaml field should primarily contain characters used in English.
The package description is too short. (-19 points)
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.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.