Command line functionality (flutter#17)

* Add command-line functionality to generate constants.

Author: lrhn

AUTHORS

@@ -3,4 +3,7 @@
 #
 #   Name/Organization <email address>
 
-Google Inc.
+Lasse R.H. Nielsen, https://github.com/lrhn
+Kevin Moore, https://github.com/kevmoo
+Phil Quitslund, https://github.com/pq
+Greg Lowe, https://github.com/xxgreg

CHANGELOG.md

@@ -1,3 +1,11 @@
+## 1.2.0-nullsafety.2
+
+- Add command line functionality to generate constants.
+  Allows clients to generate their own constants instead of
+  depending on the package at run-time.
+  Example: To generate the characters needed
+  for a hexadecimal numeral, run `pub run charcode a-fA-F\d+-`.
+
 ## 1.2.0-nullsafety.1
 
 - Allow 2.10 stable and 2.11.0 dev SDK versions.
@@ -8,17 +16,15 @@
 
 ## 1.1.3
 
-- Added example, fixed recommended lints.
+- Added example, changed lints.
 
 ## 1.1.2
 
 - Updated the SDK constraint.
 
 ## 1.1.1
 
-- Spelling fixes.
-
-- Linting fixes.
+- Spelling and linting fixes.
 
 ## 1.1.0
 

CONTRIBUTING.md

@@ -1,33 +1,30 @@
-Want to contribute? Great! First, read this page (including the small print at
-the end).
-
-### Before you contribute
-Before we can use your code, you must sign the
-[Google Individual Contributor License Agreement](https://cla.developers.google.com/about/google-individual)
-(CLA), which you can do online. The CLA is necessary mainly because you own the
-copyright to your changes, even after your contribution becomes part of our
-codebase, so we need your permission to use and distribute your code. We also
-need to be sure of various other things—for instance that you'll tell us if you
-know that your code infringes on other people's patents. You don't have to sign
-the CLA until after you've submitted your code for review and a member has
-approved it, but you must do it before we can put your code into our codebase.
-
-Before you start working on a larger contribution, you should get in touch with
-us first through the issue tracker with your idea so that we can help out and
-possibly guide you. Coordinating up front makes it much easier to avoid
-frustration later on.
-
-### Code reviews
-All submissions, including submissions by project members, require review.
-
-### File headers
-All files in the project must start with the following header.
-
-    // Copyright (c) 2015, the Dart project authors.  Please see the AUTHORS file
-    // for details. All rights reserved. Use of this source code is governed by a
-    // BSD-style license that can be found in the LICENSE file.
-
-### The small print
-Contributions made by corporations are covered by a different agreement than the
-one above, the
-[Software Grant and Corporate Contributor License Agreement](https://developers.google.com/open-source/cla/corporate).
+# How to Contribute
+
+We'd love to accept your patches and contributions to this project,
+but any larger change should be discussed using the issue tracker
+before submitting a pull request.
+There are a few other guidelines you need to follow.
+
+## Contributor License Agreement
+
+Contributions to this project must be accompanied by a Contributor License
+Agreement. You (or your employer) retain the copyright to your contribution;
+this simply gives us permission to use and redistribute your contributions as
+part of the project. Head over to <https://cla.developers.google.com/> to see
+your current agreements on file or to sign a new one.
+
+You generally only need to submit a CLA once, so if you've already submitted one
+(even if it was for a different project), you probably don't need to do it
+again.
+
+## Code reviews
+
+All submissions by non project members require review.
+We use GitHub pull requests for this purpose. Consult
+[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
+information on using pull requests.
+
+## Community Guidelines
+
+This project follows
+[Google's Open Source Community Guidelines](https://opensource.google/conduct/).

README.md

@@ -1,56 +1,60 @@
-Character code constants.
+-[![Build Status](https://travis-ci.org/lrhn/charcode.svg?branch=master)](https://travis-ci.org/lrhn/charcode)
+-[![Pub](https://img.shields.io/pub/v/charcode.svg)](https://pub.dev/packages/charcode) -
 
-[![Build Status](https://travis-ci.org/dart-lang/charcode.svg?branch=master)](https://travis-ci.org/dart-lang/charcode)
-[![Pub](https://img.shields.io/pub/v/charcode.svg)](https://pub.dev/packages/charcode)
+# Character code constants
 
-These libraries define symbolic names for some character codes.
+This package defines symbolic names for some character codes (aka. code points).
 
-## Using
+They can used when working directly with characters as integers,
+to make the code more readable: `if (firstChar == $A) ...`.
 
-Import either one of the libraries:
+This is not an official Google package, and is not supported by Google.
+
+## Usage
 
+Import either one of the libraries:
 ```dart
 import "package:charcode/ascii.dart";
 import "package:charcode/html_entity.dart";
 ```
-
 or import both libraries using the `charcode.dart` library:
-
 ```dart
 import "package:charcode/charcode.dart";
 ```
 
-# Naming
+## Naming
 
 The character names are preceded by a `$` to avoid conflicting with other
-variables due to the short and common names (for example "$i").
+variables, due to their short and common names (for example "$i").
 
-The characters that are valid in a Dart identifier directly follow the `$`.
+Characters that are valid in a Dart identifier directly follow the `$`.
 Examples: `$_`, `$a`, `$B` and `$3`. Other characters are given symbolic names.
 
-The names of letters are lower-case for lower-case letters, and mixed- or
-upper-case for upper-case letters. The names of symbols are all lower-case,
+The names of letters are lower-case for lower-case letters (`$sigma` for `σ`),
+and mixed- or upper-case for upper-case letters (`$Sigma` for `Σ`).
+The names of symbols and punctuation are all lower-case,
 and omit suffixes like "sign", "symbol" and "mark".
-Examples: `$plus`, `$exclamation`
+Examples: `$plus`, `$exclamation`, `$tilde`.
 
 The `ascii.dart` library defines a symbolic name for each ASCII character.
-For some characters, it has more than one name. For example the common `$tab`
-and the official `$ht` for the horizontal tab.
+Some characters have more than one name. For example the common name `$tab`
+and the official abbreviation `$ht` for the horisontal tab.
 
 The `html_entity.dart` library defines a constant for each HTML 4.01 character
-entity, using the standard entity abbreviation, including its case.
+entity using their standard entity abbreviation, including case.
 Examples: `$nbsp` for `&nbps;`, `$aring` for the lower-case `å`
 and `$Aring` for the upper-case `Å`.
 
-The HTML entities includes all characters in the Latin-1 code page, greek
+The HTML entities include all characters in the Latin-1 code page, greek
 letters and some mathematical symbols.
 
-The `charcode.dart` library just exports both `ascii.dart` and
-`html_entity.dart`.
+The `charcode.dart` library exports both `ascii.dart` and
+`html_entity.dart`. Where both libraries define the same name,
+the HTML entity name is preferred.
 
-# Rationale
+## Rationale
 
-The Dart language doesn't have character literals. If that ever happens, this
-library will be irrelevant. Until then, this library can be used for the most
-common characters.
-See [request for character literals](http://dartbug.com/4415).
+The Dart language doesn't have character literals.
+If that ever changes, this package will become irrelevant.
+Until then, this package can be used for the most common characters.
+See [http://dartbug.com/4415](request for character literals).

analysis_options.yaml

@@ -1,47 +1,12 @@
-include: package:pedantic/analysis_options.yaml
-analyzer:
-  strong-mode:
-    implicit-casts: false
+# Copyright (c) 2020, the Dart project authors.  Please see the AUTHORS file
+# for details. All rights reserved. Use of this source is governed by a
+# BSD-style license that can be found in the LICENSE file.
 
+include: package:pedantic/analysis_options.1.9.0.yaml
+analyzer:
+  errors:
+    annotate_overrides: ignore
+    prefer_single_quotes: ignore
+    use_function_type_syntax_for_parameters: ignore
   enable-experiment:
-  - non-nullable
-
-linter:
-  rules:
-    - avoid_empty_else
-    - avoid_init_to_null
-    - avoid_null_checks_in_equality_operators
-    - avoid_unused_constructor_parameters
-    - await_only_futures
-    - camel_case_types
-    - cancel_subscriptions
-    - constant_identifier_names
-    - control_flow_in_finally
-    - directives_ordering
-    - empty_catches
-    - empty_constructor_bodies
-    - empty_statements
-    - hash_and_equals
-    - implementation_imports
-    - iterable_contains_unrelated_type
-    - library_names
-    - library_prefixes
-    - list_remove_unrelated_type
-    - non_constant_identifier_names
-    - overridden_fields
-    - package_api_docs
-    - package_names
-    - package_prefixed_library_names
-    - prefer_equal_for_default_values
-    - prefer_final_fields
-    - prefer_generic_function_type_aliases
-    - prefer_is_not_empty
-    - slash_for_doc_comments
-    - test_types_in_equals
-    - throw_in_finally
-    - type_init_formals
-    - unnecessary_brace_in_string_interps
-    - unnecessary_const
-    - unnecessary_new
-    - unrelated_type_equality_checks
-    - valid_regexps
+    - non-nullable