One of the key tenants that alien developers should follow is that less than 100% test and documentation coverage within the project should never happen.

This isn't because I'm mean, or I have a perverted view of exactly what kinds of guarantees tests provide. It is, however, the best line of defense against regressions when actual testing time is limited.

Less than 100% test coverage poses a security risk, and lets regressions sneak by with new features.

Less than 100% documentation coverage means that in rare cases, developers have to read source in order to use the library.

This should be rectified with:

• At least one test for each alien option
• A fully-documented JSDoc typedef for the alien options, and parameter documentation for alien itself.

Quick-options are described in the project. They are a way of assigning alien options with the smallest possible substring.

A valid quick-option: {c: {c: true}} -> {control: {createBlankProperty: true}}

Business Rules

There are two passes:

• The take pass
• The case-take pass

In any of these passes, the first match becomes the matched option.

Take Pass

The take pass will take the given short-option and match it with the first matching property beginning with the substring.

For instance, con would match control but not outofcontrol.

case-take pass

The case-take pass will take the given short-option and match it with the first property which matches it, based on the first letters parsed from the word in camel-case.

Camel Case resolutions

objectUtilities -> ou
allowUnsafeInitialization -> aui

au would match aui in the above case.