ketting
The HATEOAS client for javascript (by badgateway)
appy
A functional wrapper around Fetch API (by contactlab)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
| ketting | appy | |
|---|---|---|
| 5 | 1 | |
| 542 | 63 | |
| 0.9% | - | |
| 5.6 | 7.9 | |
| 6 months ago | 25 days ago | |
| TypeScript | TypeScript | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
ketting
Posts with mentions or reviews of ketting.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-14.
-
What's the typical way for a RESTful API to tell clients what content types are supported?
So Accept does work as a response header, specifically for this case. I usually prefer to not do this extra request though. Since you're already using a hypermedia format, usually you can also include a type parameter. HAL supports this for example. Would strongly suggest you don't invent your own format. I do a lot of hypermedia APIs, we also wrote a client
-
What could be the reason why you would still chose REST over GraphQL or gRPC for your API?
I prefer REST and using HATEOAS. Its fantastic, check it out: https://restfulapi.net/hateoas/ And using tooling like https://github.com/badgateway/react-ketting and https://github.com/badgateway/ketting Makes everything extremely clean and much more simple.
-
Roy Fielding's Misappropriated REST Dissertation
I'm trying to (help) solve this:
https://github.com/badgateway/ketting - react-query: A magical way to fetch data in React
-
Typed fetch requests
Our client is open source and we've been developing it for over 4 years: https://github.com/badgateway/ketting , plus we got react bindings so you can also use resource as such:
appy
Posts with mentions or reviews of appy.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-04.
What are some alternatives?
When comparing ketting and appy you can also consider the following projects:
ky - 🌳 Tiny & elegant JavaScript HTTP client based on the browser Fetch API
fp-ts-rxjs - fp-ts bindings for RxJS
react-ketting - Ketting bindings for React
effect - An ecosystem of tools to build robust applications in TypeScript.
dragon - ⚡Fast , simple expressive web framework for deno 🦕.
blog - Code examples for my personal blog
API Platform - Create REST and GraphQL APIs, scaffold Jamstack webapps, stream changes in real-time.
bukubrow-webext - WebExtension for Buku