A Set implementation which supports Objects.
Types for Iconify data
A JavaScript parser built from the Hermes engine
Polyfill of future proposal for `util.parseArgs()`
minimal implementation of a PassThrough stream
Create and parse HTTP Content-Type header
Caseless object set/get/has, very useful when working with HTTP headers.
A helper to optimistically set Symbol.toStringTag, when possible.
Bitfield that allocates a series of small buffers to support sparse bits without allocating a massive buffer
Parses set-cookie headers into objects
Access deep object properties using a path
Underlying schema language parsed from arktype syntax.
Set nested properties on an object using dot notation.
set blocking stdio and stderr ensuring that terminal output does not truncate
request body parsing for co
Traverse JSON Schema passing each schema object to callback
Call a specified method on each value in the given object.
gRPC utility library for loading .proto files
JavaScript utilities for Vega.
A collection of standard object serializers for Pino
An implementation of the Unicode UTS #46: Unicode IDNA Compatibility Processing
An Object.keys replacement, in case Object.keys is not available. From https://github.com/es-shims/es5-shim
Elegant terminal spinner
ProseMirror's rowspan/colspan tables component
Set Content-Type metadata for S3 objects after syncing.
A simple set of types for validation of ruby objects.
Sinatra runtime and testing extensions used commonly by Thumblemonks. For example, :json_response, which turns an object into JSON and sets the content-type appropriately.
Praxis Blueprints is a library that allows for defining a reusable class structures that has a set of typed attributes and a set of views with which to render them. Instantiations of Blueprints resemble ruby Structs which respond to methods of the attribute names. Rendering is format-agnostic in that it results in a structured hash instead of an encoded string. Blueprints can automatically generate object structures that follow the attribute definitions.
Gem that allows for pretty printing data over multiple lines and with indentation, and works with objects as well as basic data types. Also allows color, and loading settings via a YAML config file.
A tool for deploying complete HTML Apps to S3-compatible object storage. Cache-Control max-age headers are set based on file type. Closync uses the fog gem to interact with both local and remote storage.
The basic_settings gem provides a way to define settings objects that define the structure of application settings, i.e. the various fields that can be set, and their types. It provides type checking, defaults inheritance, and hierarchical structure.
Provides a lightweight solution for object-oriented enumerations in Ruby in a similar ways as other languages, like Java, do. It consists of a single class (Enum), that can be subclassed to create enumerated types. Each class has a set of predefined instances, that represent the enumerated values. Fatures like support for inheritance and declaring instance methods on enumerated values are supported as well.
Provides batch loading (MGET / pipeline) for Redis::Objects attributes on ActiveRecord models, following the same design as ActiveRecord's `preload`. Supports counter, value, list, set, sorted_set, and hash_key types.
A simple Gem to enable any `ActiveRecord::Base` object to store a set of attributes in a set like structure represented through a bitfield on the database level. You only have to specify the name of the set to hold the attributes in question an the rest is done for you through some fine selected Ruby magic. Here is a simple example of how you could use the gem: class Person < ActiveRecord::Base has_set :interests end To get this to work you need some additional work done first: 1. You need an unsigned 8-Byte integer column in your database to store the bitfield. It is expected that the column is named after the name of the set with the suffix `_bitfield` appended (e.g. `interests_bitfield`). You can change that default behavior by providing the option `:column_name` (e.g. `has_set :interests, :column_name => :my_custom_column`). 2. You need a class that provides the valid values to be stored within the set and map the single bits back to something meaningful. The class should be named after the name of the set (you can change this through the `:enum_class` option). This class could be seen as an enumeration and must implement the following simple interface: * There must be a class method `values` to return all valid enumerators in the defined enumeration. * Each enumerator must implement a `name` method to return a literal representation for identification. The literal must be of the type `String`. * Each enumerator must implement a `bitfield_index` method to return the exponent of the number 2 for calculation the position of this enumerator in the bitfield. **Attention** Changing this index afterwards will destroy your data integrity. Here is a simple example of how to implement such a enumeration type while using the the `renum` gem for simplicity. You are free to use anything else that matches the described interface. enum :Interests do attr_reader :bitfield_index Art(0) Golf(1) Sleeping(2) Drinking(3) Dating(4) Shopping(5) def init(bitfield_index) @bitfield_index = bitfield_index end end
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. This works only on plural requests. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.