danabra.mov
my blog https://overreacted.io
Update index.md (#862)
* Update index.md
Subject-verb agreement in JSX over the wire
* Update index.md
Instead or -> instead of
authored by
Douglas Wade
and committed by
GitHub
3bab2ba7
de54a753
+2
-2
public/jsx-over-the-wire/index.md
+2
-2
public/jsx-over-the-wire/index.md
···
317
317
318
318
This seems useful but what if `/api/post/123` gets called from other screens that don't need this information--and you'd rather not slow them down? Maybe there could be an opt-in like `/api/post/123?expand=friendLikes`?
319
319
320
-
Anyway, the point I'm trying to make here is not that it's *impossible* to design a good REST API. The vast majority of apps I've seen works this way so it's at the very least doable. But anyone who designed one and then worked on it for more than a few months knows the drill. *Evolving REST endpoints is a pain in the ass.*
320
+
Anyway, the point I'm trying to make here is not that it's *impossible* to design a good REST API. The vast majority of apps I've seen work this way so it's at the very least doable. But anyone who designed one and then worked on it for more than a few months knows the drill. *Evolving REST endpoints is a pain in the ass.*
321
321
322
322
It usually goes like this:
323
323
···
467
467
468
468
### Backend For Frontend
469
469
470
-
Instead or *replacing* your existing REST API, you can add a new *layer* in front of it:
470
+
Instead of *replacing* your existing REST API, you can add a new *layer* in front of it:
471
471
472
472
```js {1-2,4-6}
473
473
// You're adding new screen-specific endpoints...