You make the endpoint first, and test it without the UI. What challenges do you foresee here?
Re:Monorepos: Please don’t
by gdfasfklshg4 on Thursday January 03, 2019 @09:32AM
(#18815314)
* Changing graphql schemas.
* Any non-backwards compatible change in the interface between the components. Yes this can be solved. But when working in a smaller team on proprietary software why use time solving a problem you don't need to solve?
(This is from experience.)
> why use time solving a problem you don't need to solve?
Unless they're running on the same computer and deploy literally simultaneously, this is already a problem you need to solve.
Re:Monorepos: Please don’t
by gdfasfklshg4 on Friday January 04, 2019 @06:07AM
(#18823186)
A surprising number of companies are prepared to accept an hour of downtime for an internal system if it saves them money.. In my experience the best business practice is to offer the product owner/manager the costed options in such a situation and allow them to choose.
In my experience, that is almost never the case. Often, the frontend requires a new endpoint or a modification to an existing endpoint. If you don't coordinate this change, you end up with a non-functional PR that cannot even be tested. Same happens when the backend proposes an endpoint change that affects the frontend.
We have moved the frontend and backend to the same repo to make coordination and testing of such cases simpler.