@phoneboy That doesn’t sound addictive, just preferential.
I used to walk around with a paper book in hand all the time and be reading that everywhere. The phone just makes that easier for anyone to do - big hardcovers especially suck.
@phoneboy That doesn’t sound addictive, just preferential.
I used to walk around with a paper book in hand all the time and be reading that everywhere. The phone just makes that easier for anyone to do - big hardcovers especially suck.
@konrad JSONAPI throws that back on the client - if you need some related data, you have ask for it. (And then do the join by ID locally.)
/@matigo
@matigo Often it’s because the new resource is literally just what you told it, so it’d be redundant to send it right back: clients should hold onto the request body themselves.
Sounds like that’s not the case here, though!
Reading random papers I squirreled away in Notability. Relaxing.
Limpware & limplock are new to me. Some useful gotchas for any programmer of timeouts, retries, or queues.
@matigo Contrasting CalVer [calver.org] and SemVer makes clear which is simpler to use and communicate.