But Why have a different repo ?

[Karyum]

Why have this repo for an API when you can make the API in the same repo that you are doing the frontend at. please try and convince me that you need this. cause other teams couldn't it just says that you might not know how to manage your file structure when you have a big backend and a big frontend. there are massive projects out there with only 1 package.json.

if we were start an argument about this make it a good one.

[idantb101]

it is a temporary app to deal with serving json in a way of the server.

[Karyum]

@idantb101 I know i see that 😄 but why does it need to be here and not in your actual project's file structure ?

[idantb101]

It is the not over complicate the react learning process.

[Karyum]

i dont get it what does react learning process has to do with your backend ? how can it complicate the process for you or for your team, it's just going to be harder to learn react cause when you get the data from the server, you need the server's and react's code. and you have both of them in different repos that means different code editor windows opened, that means more complicated way to develop a website using react.

if you feel this is easier for you then i will need @haithhawk @sophieeejw @NickP123 @idantb101 approval on this, ( approve this by commenting on this issue )

[idantb101]

this was a team decision in the morning stand-up.

[Karyum]

@idantb101 ok so ? i still need to know what each one of the team members think @NickP123 @haithhawk @sophieeejw