Design doc review #3 - Backend and Frontend routes about robinhoot HOT 5 CLOSED

The corporateContainer was initially for passing corporate information (ceo, employee count, headquarter location) to the stocks detail page, but I dont think that will be necessary if I am using stock api data. Do I still need to remove it?

from robinhoot.

Backend

• I don't see routes for watchedStocks table!(the joins table)
• That being said I don't think you need historical_data either.

Frontend

• (about corporate) I see. Yes, then you can keep this component here. The stock corporation information will come through the stock API but you still need a react component to show info on the browser.

from robinhoot.

• I don't see routes for watchedStocks table!(the joins table)
  For the above task, I wasn't sure how to write a joins table routes. I thought it was referenced via associations.

from robinhoot.

please let me know if I did the backend routes correctly

from robinhoot.

Looks great! I will close this issue

from robinhoot.