Alternative JSONApi serializer inspired by Netflix's fast_jsonapi serializer

Easily handle JSON in Test::Unit

JSON command line tools

General purpose JSON API client

Console tool for inspecting JSON.

Pre-parser for JSON that removes C/C++ style comments and whitespace from formatted JSON, similar to https://github.com/getify/JSON.minify.

Ruby implementation of http://goessner.net/articles/JsonPath/.

A simple JSON-RPC library, which defaults to using Faraday for the http-client wrapper.

JSON serializing support for JSON-RPC Objects. JSON-RPC Objects is complete implementation of JSON-RPC objects with respect to specifications compliance and API backward compatibility.

Json Schema Client is a Ruby client for JsonSchema with validation and hypermedia.

Object builder based on JSON-Schema

Push parser for RFC7464 JSON Sequences

RSpec matchers and Cucumber steps for testing JSON content

Gem para integração de pagamento via pix e carteira digitais da Justa

API client for Justimmo

JustRelate is a professional cloud CRM built for Ruby. For more information about JustRelate, please visit https://justrelate.com/.

It is useful to create the share buttons on sites, blog & apps to increase your range

Create JSON Signature and encryption structures

This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace

Simple solution for organizing 2 way syncing between kafka clusters