Need to allow for the creating, updating and editing of new accounts.

Need to implement a home page. Populate it with general financial information of some description:

• Will start off with a RSS feed component that will read information from a third party site.

When creating a new user, and subsequently clicking save. The user information isn't correctly displayed. Could be that the token isn't correctly saved to the client for parsing.

Need to implement a dashboard screen which will contain charts outlining expenditure, budget, upcoming bills etc.

Need to stop sending the users Full Name in a session variable - get it from the JWT token itself.

Need to be able to create and update Categories for transactions. This will need to be done through a management screen. Need to have the ability to create sub-subcategories, and assign them to parent categories. A tree view component of some description?

• Allow adding, updating and deleting of categories inline.

Need to create a message service which will manage all errors and general information returned from the server and display them to the user (and log them).

Need to facilitate authorisation in the application. This will be accomplished by using JWT the returned token will get stored on the users machine, and will ultimately get submitted on each request.

Need to add in the ability to manage (create, update and delete) transactions for each account.

Need to try and get Lazy Loading working with the routes and webpack. Also need to get Express to use the HTML file and populate it with the generated webpack files.

Need to move the karma, helpers and other config files to the config folder and ensure that everything works from there.

https://css-tricks.com/snippets/css/a-guide-to-flexbox/

note: Prefix the commit with Fixes #issue_number - this will automatically close the issue

Create a generic datasource class, that will cater for any type (REST, XML) of request to a server. The specific implementations will work out how to interpret the data from the server.

Needs to have the ability to emit an error message if there's a problem with anything - which will allow listening components to pick it up.

Leverage some of the new features described here: https://medium.com/@jrshenrique/create-a-fullstack-react-express-mongodb-app-using-docker-c3e3e21c4074?mkt_tok=eyJpIjoiT1RGa05ETmxOemMxWXpSbCIsInQiOiJCaG5SeW1CWHh1b2JSWE0zYTBTQTFTakgwMWJnaFkxeXJwc2hpVHpSbHhrc1wvZ01hVU1RUWJFWFwvNVJsWkpvZzNBdU1Ob3BkYnlRc3dxdHR1NzkrZ2wwZkdmZ1wvSDFldnVhTVNneGlvSm0zVytNZEl6WjVTdDhKd1FScm8yRnVMUiJ9

Need to move relevant items to docker containers i.e. mongo, the server code off the top of my head.

Need to implement flex grid in the application as the support for flex box in angular seems to have wained: https://css-tricks.com/snippets/css/complete-guide-grid/

Need to move all the related components into their own modules and import them in accordingly.

• Account Module
• Authorisation Module

Need to define a standard response payload for successful requests to the server, along with a standard error response:

Successful feed:

{
  $totalResults: 50,
  $startIndex: 1,
  $itemsPerPage: 10
  $records: [
    {
      $id: 1,
      name: 'Current',
      openingBalance: 500.43
    },
    {
      $id: 2,
      name: 'Credit Card',
      openingBalance: 0.0
    }
  ]
}

Successful record:

{
  $id: 1,
  name: 'Current',
  openingBalance: 500.43
}

Error Response:

{
  $diagnoses: [
    $severity: 'error', //warning, or information
    $message: 'There was an error saving the record.'
    $applicationCode: '1234',
    $entity: 'Account'
    $records: [
      {
        $id: 1,
        name: 'Current',
        openingBalance: 500.43
      } 
    ]
  ]
}

Need to convert the server-side code to typescript, and set up a compiler to handle it. This will facilitate the user of async and await in the relevant functions.

http://brianflove.com/2016/11/08/typescript-2-express-node/
http://brianflove.com/2016/10/04/typescript-declaring-mongoose-schema-model/

• Update project to use ES6 (including getting the tests to work)

• Make use of Async/Await

• Handle Errors

This follows in from the best practices in the following URL: https://www.codementor.io/mattgoldspink/nodejs-best-practices-du1086jja

Use swagger-express to provide information on all of the api routes available.

• Investigate using GraphQL as a replacement for the server-side REST implementation using node.
• See how it plays with Swagger.

Use Angular to facilitate localisation for the project.

Need to run "./node_modules/.bin/ng-xi18n" to generate the relevant files. See: https://angular.io/docs/ts/latest/cookbook/i18n.html

Researching that a bit more, seems like it wouldn't be something that could be used in services for instance - with regards to any messages that need to be returned to the user. A better approach would probably be something like: https://scotch.io/tutorials/simple-language-translation-in-angular-2-part-2

try and make use of the lodash get method.

Currently there is no coverage reporting for the client (or server) Need to get this implemented for the project.

Need to create a new component for navigation items, and remove the dependency to the auth component. Favour property binding. Also need to facilitate submenus

Need to leverage webpack for the server-side code in the project. Specifically need to copy the log4js config file to the dist directory after it's been compiled.

Need to create a tree view component which will allow for drag and drop functionality to their respective nodes. Should

Might need some sort of TreeNode component to facilitate this?

• Id - the Id of the relevant record.
• Name - the name of the node.
• Parent - the parent of the node.
• Children - This is an array of child TreeNode's
• Expanded - true, when it's open.
• CanDrop - true if this node accepts being dropped on.

Need to create a Service that will actually emit each of the events for the TreeNode, they include:

• NodeDropped - The node that was dropped on another
• NodeExpanded - Which node was expanded.

Asynchronous action:

• Get a list of all the parent records. Those without a child. (Add where clause support to the datasource component?)
• Mark all of these with a + image
• If the user clicks on the + make a call to the server to return all the child elements.
• Dynamically add these child elements to the clicked parent. Have the position of the clicked parent. (How does angular do this?)

Synchronous

• Get all the data,
• Build up all the nodes based on the JSON received. Nesting as we process.

NOTE: Since this component works off events, it will be up to the relevant component which implements this, to dynamically create the nodes in situ when the click event has been intercepted - specifically for asynchronous processing.

See about integrating this with codeship.

Have a look at the following website and implement appropriate recommendations: https://www.codementor.io/mattgoldspink/nodejs-best-practices-du1086jja

• Add scripts to package.json

• Make use of environment variables

• Use logging library (log4js)

• Use Helmet to secure application