Vicki, once a manager of aircraft maintenance, is now charming Python & Ruby. She has coded OpenGates.dev, #VetsWhoCode bot, Code Questions bot, & LGBTQ of the Day Bot. They love relatable writing.
Location
Richmond, Virginia
Education
Self Taught Python/Ruby, BBA in Small Business Mgmt, AS in Production Mgmt
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.
Vicki, once a manager of aircraft maintenance, is now charming Python & Ruby. She has coded OpenGates.dev, #VetsWhoCode bot, Code Questions bot, & LGBTQ of the Day Bot. They love relatable writing.
Location
Richmond, Virginia
Education
Self Taught Python/Ruby, BBA in Small Business Mgmt, AS in Production Mgmt
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.
Okay. I think I get it now. Thanks!