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

I have another one for you. GraphQL should never be used as a way to "GET-modify-PUT" records, but often is, because why reinvent GET if you already have GraphQL? Because the query specifies the fields, so if new fields are added to existing types, existing clients don't receive them and PUT the record back without those fields. You now have to try to deal with this in the backend, with subtle and severe edge cases potentially affecting the backend and all of its clients.


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

Search: