Wissenkarten Projekt - Integrate Stocks service

Guten Tag Community. Willkommen auf Wissenkarten Projekt.

Note: We wish to close the challenge as soon as possible as we need the solution quickly. Hence, please note that we may close the challenge by 31 March 2015

 

Project Overview
Wissenkarten Projekt is an application that provides many services to the end user is the form of "knowledge cards". Think of these as widgets with additional functionality associated with them.

 

Challenge Details

We have an application that has the both the front end and the back end but they do not communicate with each other.

We have also developed a stock service.

 

As part of this challenge your task is as follows:

1. The application already contains a weather service and general knowledge service. You now need to integrate the stock module
2. Go through the docs/vRexPayloads.pdf file. Check out the Stocks related payload. This is just an example payload.
3. Update the routes (if required) to access the newly integrated stock service. Also, ensure that you update the routes in config/routes.js
4. All the stock endpoints should return json responses. However, the json response willl contain the HTML template to show in the UI. This template will contain the stock response. Use whiskers templating engine.
5. On the user interface, display the response of the stock service using the template sent through the json response.
6. Your template should match the one in the prototype for the stock card. Use the left and right arrow keys to slide through the cards after launching the application.

Note the application flow:

1. A request will come for http://<domain>?q=<payload>. Client should call the /api/service route to get the list of available services for that payload.
2. Client will get a list of endpoints that it needs to call. It will loop over them and collect all the responses.
3. Each successfull response is a card in the carousel.
4. Store each request in the database.

Step 1 and 4 have already been carried out. Please check out the Deployment Guide in detail before you start making changes.

If an endpoint cannot return a response for some reason (such as the payload passed does not contain the parameters that it requires), do not show a card for it. Show card only for successfull responses and remember to follow the existing template for stock cards.

Don't make any other changes. Running tests through $ grunt test should still work.

Final Submission Guidelines

Submit the application in a zip file

The winning submission will be asked to create a pull request to our gitalb repository.