overhaul to the getQuery helper function. it now takes these parameters:
neo4j query string
query parameters object
res object (getQuery will not handle sending the HTTP response)
singleEntity boolean indicating whether the query is expected to return an array or a single object
mapper function that each 'row' returned from the DB is sent through. this gives us the chance to do transofmrations before returning data to the UI
updated GET /users, GET /products, GET /products/:productId, GET /products/popular, and GET /images/:imageId based on this. these are the services the UI is most dependent on right now.
commented out all other services so that the mocks will be triggered until we can get them updated. will need to set up a similar pattern for post/put/delete requests.
I wasn't sure if you intended to merge this before @bhaveshmjain had had a chance to review but it's helpful to me to pull these changes in (via master of course)
overhaul to the getQuery helper function. it now takes these parameters:
updated
GET /users
,GET /products
,GET /products/:productId
,GET /products/popular
, andGET /images/:imageId
based on this. these are the services the UI is most dependent on right now.commented out all other services so that the mocks will be triggered until we can get them updated. will need to set up a similar pattern for post/put/delete requests.