
Just released version 3.0 of our #lowcode platform: row-based security, @jsonapi and @odataorg endpoints for relational, graph, and document DBs, support for stored procedures, multiple result sets, and much more... github.com/dashjoin/platform


Just released version 3.0 of our #lowcode platform: row-based security, @jsonapi and @odataorg endpoints for relational, graph, and document DBs, support for stored procedures, multiple result sets, and much more... github.com/dashjoin/platform

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 @jsonapi implementation. https://t.co/Sdwk2wH7U1

We use JSON:API and it is the best! Paints your bikeshed.
JSON:API v1.1 has just been finalized! 🎉 Thanks to the many contributors and implementors who have helped make this happen. jsonapi.org/format/

We're utilizing JSON:API heavily for our new APIs!
JSON:API v1.1 has just been finalized! 🎉 Thanks to the many contributors and implementors who have helped make this happen. jsonapi.org/format/

I worked with JSON:API for @spreecommerce it was great fun.

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

We recently opened up our API to our partners @Climate_Clever and adopted @jsonapi. 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} 101: a REST API standard every backend developer needs to know. A few months ago I built a public API following the @jsonapi specification. I liked it very much as it covered simply all the needs I had. A thread 🧵

I'd strongly recommend taking look at the @jsonapi 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.

We're also thrilled to announce today that @jelhan1 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-api…

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-api…

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/blog/d…

When I started to triage issues for @jsonapi 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. 💪
Last week I started to triage open issues and merge request for @jsonapi to help getting v1.1 out of the door. If you are eager to help, do not hesitate to reach out to me! It was fun so far and I learned a lot by doing it. There are many ways you could contribute. 👇

Thanks @jelhan1 for your contributions and for inspiring others to contribute!
Last week I started to triage open issues and merge request for @jsonapi to help getting v1.1 out of the door. If you are eager to help, do not hesitate to reach out to me! It was fun so far and I learned a lot by doing it. There are many ways you could contribute. 👇

Following the @jsonapi 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.
Excited to be trying out the @jsonapi atomic operations extension in an application I’m working on: jsonapi.org/ext/atomic/

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