JSON:API topic
JSON:API is a specification for how a client should request that resources be fetched or modified, and how a server should respond to those requests. JSON:API is designed to minimize both the number of requests and the amount of data transmitted between clients and servers. This first draft was extracted from the JSON transport implicitly defined by Ember Data’s REST adapter. In general, Ember Data’s goal is to eliminate the need for ad-hoc code per application to communicate with servers that communicate in a well-defined way. The REST Adapter in Ember Data implicitly defined a protocol that custom servers could implement to get a drop-in client for all of their resources. The goals of the media type are to balance:
- A generic media type that can work across a broad set of use cases, including the generally used relationship types
- Similarity to existing server-side framework practices (and human readability for debugging)
- Ease of implementation on the server side
- Ease of implementation on the client side
This specification reached a stable version 1.0 on May 29, 2015.
tslog
📝 tslog - Universal Logger for TypeScript and JavaScript
ja_serializer
JSONAPI.org Serialization in Elixir.
JsonApiDotNetCore
A framework for building JSON:API compliant REST APIs using ASP.NET and Entity Framework Core.
json-api-normalizer
Normalize JSON API data for redux applications
lux
Build scalable, Node.js-powered REST JSON APIs with almost no code.
simpla
Open, modular, and serverless content management for a modern web
json.h
🗄️ single header json parser for C and C++
element-api
Create a JSON API/Feed for your elements in Craft.
ck
Collective Mind (CM) is a small, modular, cross-platform and decentralized workflow automation framework with a human-friendly interface and reusable automation recipes to make it easier to build, run...