/explore
|
You are here 
|
mydeveloperplanet.com | ||
| | | | |
httptoolkit.com
|
|
| | | | | It's hard to work on APIs without hearing about OpenAPI. OpenAPI is an API description format, which is essentially metadata that describes an HTTP API: where... | |
| | | | |
devopsian.net
|
|
| | | | | Discover the value of API-First design for side projects. Learn how this approach can streamline development, improve consistency, and accelerate your workflow through practical examples and code generation. | |
| | | | |
yos.io
|
|
| | | | | You're building an API. You develop a backend service with a few endpoints and deploy it to production. You publish several official language-specific API clients as well as an API documentation. The day ends on a happy note. The following day, a new feature is being added the API. You have to: Update the server implementation to support the new feature. Update all client libraries (one SDK for each supported platform and language.) Update the documentation. All the above must be consistent with each other. Also, the frontend team is blocked until your backend API is complete. You let out a heavy sigh. | |
| | | | |
apisyouwonthate.com
|
|
| | | When OpenAPI or JSON Schema documents get massive or repetitive, the contents can be split across multiple documents (on the filesystem, URLs, in memory somewhere) and joined together $ref. These split up API descriptions can then be joined back together as one document, with $ref pointing to an internal location | ||
