Lexers for different languages in Dart with Regular Expressions adapted from the awesome pygments library.
[0.0.1] - TODO: Add release date.
- TODO: Describe initial release.
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: lex: ^0.0.1
2. Install it
You can install packages from the command line:
$ pub get
$ flutter pub get
Alternatively, your editor might support
pub get or
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 Feb 13, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.7.1
- pana: 0.13.5
Health issues and suggestions
Document public APIs. (-0.90 points)
308 out of 309 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/base/lexer.dart. (-2.48 points)
lib/base/lexer.dart reported 5 hints:
line 42 col 11: Unnecessary new keyword.
line 149 col 17: DO use curly braces for all flow control structures.
line 151 col 17: DO use curly braces for all flow control structures.
line 153 col 17: DO use curly braces for all flow control structures.
line 155 col 17: DO use curly braces for all flow control structures.
lib/base/token.dart. (-1 points)
lib/base/token.dart reported 2 hints:
line 110 col 5: Don't explicitly initialize variables to null.
line 154 col 5: Don't explicitly initialize variables to null.
lib/base/types.dart. (-0.50 points)
lib/base/types.dart reported 1 hint:
line 19 col 23: Use
= to separate a named parameter from its default value.
Maintenance issues and suggestions
Support latest dependencies. (-10 points)
The version constraint in
pubspec.yaml does not support the latest published versions for 1 dependency (
The package description is too short. (-15 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.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
lex.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
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.