Conversation

Notices

1. Olivier Forget (teleclimber@social.tchncs.de)'s status on Sunday, 19-Feb-2023 08:10:00 JST Olivier Forget

   in reply to

   • Dave Rupert
   • Alex Riviere

   @davatron5000 @fimion I tried implementing JSON:API in my project (https://dropserver.org) but while the frontend might benefit from responses with extras attached, the backend can become complex.

   Maybe part of the problem was the lack of good library for Go (IMO)? I even tried contributing to one.

   After a while the added complexity on the backend was a burden I did not want to carry.

   I ripped it all out and now I just have dumb-dumb routes like a caveman.

   https://github.com/teleclimber/Dropserver/commit/7a943afde83829894cdafd648078b6f394595417#diff-452acb3790db76418fdce8320090b7e88f723b6092e54c4d216b4a3999f8d34e

   • Dave Rupert (davatron5000@mastodon.social)'s status on Sunday, 19-Feb-2023 08:10:01 JST Dave Rupert

     • Alex Riviere

     I’m a big fan of when a project draws a line in the sand (based on experience!) and says “this is the way to do things”. So much easier to frame my opinions based on a hard line. Anyways, I asked @fimion to write about JSON:API which “standardizes” REST APIs because I’ve seen him advocate for it before and he did. The response format is okay, but I really like the URL pattern structure and I could probably clean my API up a lot. https://alex.party/posts/2023-02-17-why-i-like-json-api/

     Adrian Cochrane repeated this.