Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> and on the frontend, get prepared to write out every songle fields you need from the backend. i can imagine it may be brutal for those who have a lot of changes in their schemas.

Wouldn’t you need to do this in some form anyway (since those fields would be displayed or used in some way)?



well, it won't be just a simple GET /user/1 anymore. it will be like: user { id name role status age sex address group { id name } etc etc }


Right - what I meant was more like when you get some data you probably want to display it in the UI and would already be doing something like ‘Hi ${user.name}, your age is ${user.age}’. This is affected by schema changes irrespective of the way the API is invoked.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: