camjm / beyondearthappangular Goto Github PK

Testing with Mocha. See https://github.com/camjm/gswg-examples/tree/master/5/01-testing. Do in separate branch.

see: https://github.com/camjm/gswg-examples/tree/master/1/11-aws
and: https://github.com/camjm/gswg-examples/tree/master/4/07-project

https://docs.angularjs.org/api/ngResource/service/$resource

Credit Card Resource
Custom charge method. Do in the Game Resource for GameTechnologies, GameWorkflow etc

Cancelling Requests
See UnitListController.

Compare this repository to my other grunt source repositories:

• dynamic-predicate
• beyond-earth-tool
• beyond-earth-technologies
• gswg-project
• gswg-examples

Refactor the html views to 'src' as jade. Use appropriate file structure (not flat).

See Customizing Bootstrap (Sass) using Grunt

Apply the following AngularJS tutorials to the repository:

• Kickstart Your AngularJS Development with Yeoman, Grunt and Bower
• Tutorial / 13 - REST and Custom Services
• $resource
• Creating a CRUD App in Minutes with Angular’s $resource Demo here
• The magic of $resource (or simply a client-side Active Record)
• AngularJS ng-repeat with custom element inside a table is rendering strangely
• AngularJS Form Validation

https://scotch.io/tutorials/animating-angularjs-apps-ngview

Create a new TypeScriptBranch that uses TypeScript instead of CoffeeScript to generate the JavaScript. Compile with Babel, using a grunt plugin.

Currently our angular app is a global variable, that is referenced in lots of script files (controllers, etc). This means that we can't wrap or js generated from coffeescript in a wrapper function (see the grunt option). Instead of this, use a string passed to angular.module to access the app and wrap the js.

which grunt plug in should I use?

• main-bower-files (current plugin)
• grunt-bower-task (grunt specific - preferable)
• grunt-bower (I used this previously, see commit history, but wasn't so good)

change to using the ui-router module instead of the ngRoute module. It uses $stateParams instead of $routeParams. Then we can use $stateParams in the route defininition resolvers instead of $route ($routeParams isn't defined at that time, can only be used inside controller).

https://blog.codecentric.de/en/2014/08/angularjs-browserify/
http://codeofrob.com/entries/grunt+browserify+npm+application=success.html

Tidy up the controller naming convention. Refactor file structure so it is not flat. For example put all the unit controllers in a 'unit' folder. Controllers should follow the following pattern:

• UnitListController
• UnitViewController
• UnitAddController
• UnitEditController

This is to make the controller match the routing url pattern.

Use the Yeoman Angular Generator to add thing like new coffeescript controllers, etc.

find and use a grunt plugin for a http server (instead of just using 'http-server' from the command line).

Refactor all services as angular resources. Do not use wrapper, just return the resource object.

Investigate configurations for $routeChangeSuccess and $routeChangeError events, so we can handle failures for calls to the back-end globally. Currently we use the content-info directive in each view to handle the $promises, but instead we can handle them in the route configuration.

Because it's the routing modules responsibility to handle, not the controller's.

Incorporate angular-hateoas so the app can use the API's links. (Remember to do this in a new branch).

Use for literate programming.
See: http://jashkenas.github.io/docco/
And: https://lostechies.com/derickbailey/2011/12/14/annotated-source-code-as-documentation-with-docco/

Follow the following tutorials:

• Using Grunt + Bower with Laravel and Bootstrap
• Use Bootstrap with Bower and Grunt

Consider using ui-router instead of default ngRoute module.
See differences.