🔥Telegram İfşa

Starting today, I’ll be focusing my open source work more exclusively on two projects: JSON:API and OrbitJS. Both projects have big potential but need guidance and attention to get there. I’m glad to have you all along for the journey. Please reach out if you want to help :)

Just released one of my side projects - JSON:API library for Java/Kotlin built on top of Moshi from @squareeng Check it out on the following link... the feedback is welcomed :) github.com/MarkoMilos/jso…

Please see the results of the community chat poll below, as well as a follow up poll re: the result (open for 3 days to give folks a chance to respond).

Just finished hosting my first workshop at a conference. Feeling totally exhausted to be honest. But sharing my knowledge about JSON:API was a great experience. Thanks a lot API Conference for giving me the chance to do so!

Excited to be trying out the JSON:API atomic operations extension in an application I’m working on: jsonapi.org/ext/atomic/

Following the JSON:API extension spec worked out really well for the first iteration! The only thing that would have been useful is an example response for a mixed set of operations. It took a bit of extra reading to realize to return {} for delete operations.

Thanks @[email protected] for your contributions and for inspiring others to contribute!

When I started to triage issues for JSON:API project on GitHub, the project had 143 open issues. Since today it is done to 120. 🎉 Still some work to do, until we hit the goal of less than 100 open issues. But the work starts to pay off. 💪

Want to help shape Drupal's JSON:API's future? We've posted the decoupled and integration survey asking for feedback from you, the community. drupal.org/about/core/blo…

JSON:API v1.1rc4 has just been announced! If all goes well with this release candidate, v1.1 will be finalized on September 30. 🎉 github.com/json-api/json-…

We're also thrilled to announce today that @[email protected] is joining the team of JSON:API editors! 🥳 Jeldrik has been absolutely essential to getting the spec ready for the v1.1 release over the past year. github.com/json-api/json-…

Nate Hopkins I'd strongly recommend taking look at the JSON:API standard which has quite reasonable solutions to a lot of common API problems you may face (such as pagination, sorting, relationships / resource linking, etc). Even if you can't use it, it's still a good source of inspiration.

{json:api} 101: a REST API standard every backend developer needs to know. A few months ago I built a public API following the JSON:API specification. I liked it very much as it covered simply all the needs I had. A thread 🧵

We recently opened up our API to our partners ClimateClever and adopted JSON:API. I never thought I would enjoy building new endpoints as much as I do now. Constraints are so freeing! #API #Node #JavaScript #ClimateActionNow jsonapi.org

JSON:API v1.1 has just been finalized! 🎉 Thanks to the many contributors and implementors who have helped make this happen. jsonapi.org/format/

JSON:API I worked with JSON:API for Spree Commerce it was great fun.

We're utilizing JSON:API heavily for our new APIs!

Have you used compound documents/ resource relationships in APIs before? It helps limit API-chaining by providing resources related to your query in a single response. This and many new features are available thanks to our JSON:API implementation. bit.ly/3CzaSOL

Just released version 3.0 of our #lowcode platform: row-based security, JSON:API and OData.org endpoints for relational, graph, and document DBs, support for stored procedures, multiple result sets, and much more... github.com/dashjoin/platf…