Hybrid.angularAMD.HATEOAS

Install

After cloning:

$ npm i
$ bower i

Review Grunt "strategies":

$ grunt

Strategies

Stratgies combine Basics and Workflows to achieve certain desirable configurations.

Vendor stuff

Here's an example of adding a vendor to the build:

$ grunt add/vendor --layer=script --vendor=bower_components/angular-ui-router/release/angular-ui-router.js
$ grunt setup
$ grunt build

Removing vendors in similar fashion is easy:

$ grunt remove/vendor --layer=script --vendor=bower_components/angular-route/angular-route.js
$ bower uninstall angular-route --save
$ grunt setup
$ grunt build

Testing

1. TODO RequireJS + karma

Rationale

If the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period. Is there some broken manual somewhere that needs to be fixed?

Roy Fielding

1. Hybrid: RequireJS Modules ➢ Cordova/Ionic
2. angularAMD: RequireJS Modules ➢ AngularJS Modules
3. HATEOAS: (ORM + RequireJS Modules) ➢ Evolvable Object-ive Representations of Relational Maps (halberd + js-data looks good enough; but hypermedia libraries already provide for storing representations, etc.)

Other noteworthy points

1. TODO RequireJS Hot Swapping / Code-On-Demand
2. ngdocs on RequireJS, RequireCSS, etc.
3. ngdocs on GruntJS (really modular tasks as basics and workflows)
4. TODO Organic CSS (need to think about how to implement functional groups and common styles; so, Organic RequireCSS)
5. TODO Optimized builds (need a better way to maintain disparate shims)
6. TODO Layering: (RequireJS Modules + dualapi) ➢ Hypertext Passing for Discovery Layer (lodash is missing from browserify's dependency list)
7. TODO angular-hypermedia obeys which JSON Schema spec for Hypermedia? (HAL? Siren?)
8. TODO *chain environments for Value Layer
9. TODO lib for Attribution Layer
10. TODO Leaflet Maps common modules