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

In terms of taking an openapi specification first, then generate server/client from that approach, I have a project that focuses on this for nodejs koa and fetch/axios: https://openapi-code-generator.nahkies.co.nz/overview/about

I plan to eventually incorporate guidelines on writing good openapi specifications, and general design patterns for API.

Very much agree with most of the points in the article, such as returning objects over flat array's, supporting partial updates via PATCH.

I'm less convinced by exclusion of PUT (sometimes a client generated id / idempotent create is useful), and ability to filter collections on all fields (sounds inefficient).

Look forward to returning to this when some of the to-dos have been filled out



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

Search: