markdown guide
 

Ideally no work will need to be done to connect them. They should be wholly decoupled. They should be implemented with clear interfaces, and whomever designed the project is responsible for ensuring these interfaces are properly designed.

 

Hmm, that makes sense. But who tells the forms and stuff to do there thing?

Maybe I'm answering my own question, but I guess I've done more with forms doing backend stuff. Frontend wouldn't be worrying about get and post.

 

You'll still worry about GET and POST on the frontend - what you won't worry about is how those are implemented. You want to be able to post the right data to the right endpoint and then just assume the server's state gets updated properly. Then when you next make a GET, the data returned will reflect any changes youve made, but your frontend code doesn't need to know how or why or what, just what endpoints to hit.

 

Typically frontend consumes API provided by backend (frontend work). In ideal situation integration can be as simple as generate client from API specification, for example GraphQL (or OpenAPI, or grpc).

Classic DEV Post from Jan 16

What's your typical process for reviewing a pull request in GitHub?

I'm never sure whether I'm using this tool as effectively and efficiently as po...

Vicki profile image