Add Promise polyfill to version control. Promise objects
are included in ECMAScript 6 and browser support is
present, but non-universal. Using the polyfill approach
permits the use of Promise directly throughout the
application without relying on bleeding-edge browser
support.
Promises are useful at the framework level particularly
because of the number of asynchronous calls made when
assembling bundles. Framework layer is WTD-518.
Add top level README file describing, in broad
terms, the structure of the project. In particular,
this documents the naming conventions which support
build and test, and provides a short summary of how
these both run. WTD-519.
Include libraries in the WAR file built by the
command line build, except for those libraries
which are present only to support test execution.
Part of initial branches-and-build set up for
WTD-519.
Don't request json as an XHR response type, as this
is not supported by Phantom for command line test
execution. Part of ongoing intitial repository and
build setup for WTD-519.
Add clarifying comments to temporary files, to
ensure they are distinguishable as placeholders.
Part of developing project folder structure and
build for WTD-519.
Add libraries for Angular and Require. This expands
folder structure to support initial build (WTD-519)
and also directly supports implementation of a
framework layer (WTD-518).
Add general structure for Open MCT Web, including
top-level and second-level directory structure.
README files are included to explain the role of
each directory; markdown is used to allow for
richer display when viewer support is present.
WTD-519.
Initialize repository with gitignore file. This
will serve as the basis for the open source
master branch (and thus all other branches)
during the Angular transition. WTD-519.
