It tries to maintain the same API (to minimize the learning curve) while allowing
That said, there will be some cases where the API is a bit different. This will mostly be done to remove ambiguity in method signatures. For example, the JS SDK can be used with callbacks or with promises (in most cases). However, this package uses only Futures and does away with callbacks altogether.
This package currently doesn't expose all the functionality that the JS SDK does. However, the intention is to gradually make it feature compatible with the JS SDK.
Contributions in the form of suggestions to improve the code quality, feature requests, bug notifications, etc are all welcome.
If you have any suggestions/pull requests to improve this package, just open an issue and I'll be happy to work with you to improve this package.
You can file feature requests and bugs at the issue tracker.
Add this to your package's pubspec.yaml file:
dependencies: parse_facade: "^0.0.2"
You can install packages from the command line:
$ pub get
Alternatively, your editor might support
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|0.0.2||Nov 22, 2016|
|0.0.1||Nov 22, 2016|
We analyzed this package on Apr 23, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
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]
Detected platforms: web, other
Package is pre-v1 release.
While there is nothing inherently wrong with versions of
0.*.*, it usually means that the author is still experimenting with the general direction API.