Skip to content

Latest commit

 

History

History
26 lines (19 loc) · 1.88 KB

README.md

File metadata and controls

26 lines (19 loc) · 1.88 KB
Raw

OneFlowChallenge

Full Stack JavaScript Technical Challenge

Task 1

Frontend:

I decided to use Angular5 to display the data.
A service worker is used to cache all app data, so it should have offline support (provided you have already fetched the data at least once before).
The title filter is made client-side, so no further API requests are needed. I decided to go with server-side filtering for the seasons simply to demonstrate that the API supports season query parameters; Even though client-side filtering on seasons would be more efficient since we already fetch all available seasons on first request.

Disclaimer: PWA support for Angular CLI was just released six days ago (23. Nov) so there might be some minor issues regarding the PWA functionality.

  • To run the angular project run ng serve, start the server and navigate to localhost:4200
  • To build the angular project run ng build --prod, start the server navigate to localhost:3000
     

Backend:

  • npm t - Runs tests for /api/series routes
  • npm start - Runs the server, serving the Angular5 PWA.
  • npm run apidoc - Generates API documentation, I'm having some trouble with routing to /docs with this setup, so for now it can be accessed by opening ~/OneFlowChallenge/server/static/docs/index.html, sorry about that.

The API currently supports both POST and GET requests.

Task 2

See ~/OneFlowChallenge/task2.commented.js and ~/OneFlowChallenge/task2.suggestion.js.
As this is a PR I decided agains making error and utility/mongoose functions since they belong in either another PR or might have been done previously.