json-api
blog
| json-api | blog | |
|---|---|---|
| 63 | 22 | |
| 7,354 | 506 | |
| 0.4% | - | |
| 5.7 | 4.9 | |
| 19 days ago | 5 months ago | |
| CSS | ||
| Creative Commons Zero v1.0 Universal | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
json-api
- JSON: API – A Specification for Building APIs in JSON
-
REST API: Best practices and design
There is a group of people who set out to standardize JSON responses into a single response style, either for returning single or multiple resources. You can take their style as a reference when designing their API to ensure uniformity of responses.
-
Path To A Clean(er) React Architecture - Domain Entities & DTOs
The server seems to be using the popular JSON:API standard which is a great way to build APIs. But should we really use these data structures in the frontend?
-
Path To A Clean(er) React Architecture - API Layer & Data Transformations
Note: You think the response data structure with the data field and the included field with mixed data types looks weird? You might not have encountered the popular JSON:API standard yet.
-
Hatchify: The Fastest Way to Build JSON: APIs
In addition to saving you time on boilerplate, the API provided by Hatchify fully implements the JSON: API specification, which stipulates solid standards to define the peculiarities of CRUD REST APIs. Get back all the time spent bike-shedding how to implement standard API features like filtering, pagination, including related data, etc. JSON: API offers consistent practices for frontend and backend developers to agree on how resources are fetched and returned. Since Hatchify provides the core of your API for you, you can count on it’s standardized functionality to give your API a consistent start.
- SQL as API
-
Show HN: Sunnybox – An Email API for Effortless IMAP Integration
-JSON:API format responses (https://jsonapi.org) for better standardization.
Built using Ruby on Rails, Sunnybox is designed to offer a powerful yet easy-to-use solution for developers managing email systems.
I'd really appreciate your feedback on:
- The API's user-friendliness and efficiency.
-
What if an SQL Statement Returned a Database?
https://github.com/json-api/json-api/issues/795
There is an atomic operations extension:
-
A View on Functional Software Architecture
JSON:API to format each message
-
Custom Fields: Give Your Customers the Fields They Need
As we’re building a RESTful API that’s formatted by the JSON:API specification and store our data in a MySQL8 relational database, a few things were pretty straightforward – we need a new model and we’ll name it Custom Field (naming wasn’t an issue here 🥲).
blog
-
Show HN: Markdown HN profiles at {user}.at.hn
Probably not very: https://github.com/stickfigure/blog/wiki/Beware-cutesy-two-l...
But probably sufficient for a project like this.
-
Shots: Create Mockups
Also - the organizations that run the DNS servers of little top level domains are not necessarily competent. Back when I had a company on the .st domain, we had an 8-hour outage when something in their infrastructure broke and everyone in their organization was asleep:
https://github.com/stickfigure/blog/wiki/Beware-cutesy-two-l...
- Java Logging on Google Cloud Platform
-
How to (and how not to) design REST APIs
he actually writes about that. I happen to like it too.
https://github.com/stickfigure/blog/wiki/GitHub%27s-wiki-mak...
- How to (and how not to) design REST APIs · stickfigure/blog Wiki
- Intercom is a terrible Mailchimp. So is Mailchimp
-
What We Learned from Our Five Failed YC Applications and One Successful One
I would avoid all of the two-letter domain names. I suffered 8 hours of excruciating downtime back in 2012 when the .st nic went down:
https://github.com/stickfigure/blog/wiki/Beware-cutesy-two-l...
I learned my lesson, I'll take the .com every time, even if I have to get creative with the name.
-
Nomad drained of $150m due to a coding mistake
This is untested on ETH PoS and could result in a significant loss in value for ETH holders. Not only that, but it gets even more complicated with stablecoins that are on ETH. What makes all of this quite interesting is the exchanges who get to decide which USDC on ETH they sell to you. Likely a big reason why exchanges, like Coinbase, are some of the largest ETH stakers.
[1] https://github.com/stickfigure/blog/wiki/Proof-Of-Stake-Wear...
What are some alternatives?
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
oxen-core - Oxen core repository, containing oxend and oxen cli wallets
api-guidelines - Microsoft REST API Guidelines
solidity-underhanded-contest - Website for the Underhanded Solidity Contest
laravel-json-api - JSON API (jsonapi.org) package for Laravel applications.
consensus-specs - Ethereum Proof-of-Stake Consensus Specifications
zenstack - Typescript toolkit on top of Prisma ORM, offering flexible and declarative Access Control Policy(Authorization/Permission) for RBAC/ABAC/PBAC/ReBAC with auto-generated type-safe APIs and frontend hooks.
apollo - 🚀 Apollo/GraphQL integration for VueJS
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
grpc-swift - The Swift language implementation of gRPC.
vex - A modern dialog library which is highly configurable and easy to style. #hubspot-open-source
postman-app-support - Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.