Results for all-object-keys

underscorize_keys convert all the keys of object to underscore

Simple and Compressed Object Notation (SCON) serializes arrays and objects into a binary format, all the while using as little space as possible by reusing duplicate keys with a binary reference and clever type definitions.

Provides util methods to modify Hash objects. Currently contains a single method that converts all string keys in a Hash to symbols. Will recursively convert string keys through hashes and hashes within arrays.

DrySQL uses your DB's information schema to identify keys, and generate associations and validations for ActiveRecord objects. You defined the schema on your DB ... don't re-define it in your application code. Legacy DB Tables, Ruby Desktop apps, Rails apps...DrySQL's got all your databases covered

CollectionUtils provide with basic collection templates like stack(push, pop, peek), queues(enqueue, dequeue), heaps/tree(MinHeap, MaxHeap, BST) and HashDeserializedObject(Converts a hash into object for easy access. All the keys will become attributes of the object). Check out the wiki at https://github.com/deeshugupta/collection_utils/wiki

The otoindiff gem modifies all Ruby Hash objects to support indifferent access by default, allowing seamless use of string or symbol keys interchangeably.

The Weak library provides a Weak::Set class to store an unordered list of objects and a Weak::Map class to store a key-value map. The collection classes only hold weak references to all elements so they can be garbage-collected when there are no more references left.

Read through caching library inspired by Cache Money, support Sequel 4 Read-Through: Queries by ID or any specified unique key, like `User[params[:id]]` or `User[username: 'bachue@gmail.com']`, will first look in memcache store and then look in the database for the results of that query. If there is a cache miss, it will populate the cache. As objects are created, updated, and deleted, all of the caches are automatically expired.

In this initial build, several functions are available on the Novel object: word_count, which is self-explanatory word_frequency, which returns a hash containing key value pairs of the 'word => number_of_times_that_word_appears_in_the_text' variety word_find, which takes a string as an argument and returns the number of times the string appears in text. most_common_words, which returns each of the words that is the most common or tied for most common. All functions are case-insensitive and ignore punctuation.

Create APIs in a fast and dynamic way, without the need to develop everything from scratch. You just need to create your models and let APIcasso do the rest for you. It is the perfect candidate to make your project development go faster or for legacy Rails projects that do not have an API. If you think it through, JSON API development can get boring and time consuming. Every time you use almost the same route structure, pointing to the same controller actions, with the same ordering, filtering and pagination features. APIcasso is intended to be used to speed-up development, acting as a full-fledged CRUD JSON API into all your models. It is a route-based abstraction that lets you create, read, list, update or delete any ActiveRecord object in your application. This makes it possible to make CRUD-only applications just by creating functional Rails' models. Access to your application's resources is managed by a .scope JSON object per API key. It uses that permission scope to restrict and extend access.

this is a little chunck of code i use to dump Ruby objects to YAML with Hash keys in a some-what consistent order. i do this because i often find myself using YAML files as data storage and this makes it a lot easier to compare versions with text-based diff toolspec. this lib is horribly alpha and has no tests what-so-ever. i'm sure it's as full or bugs and bad ideas as 100 lines of code can be. i just put it here so it's easier for me to use across projectspec. but you're welcome to take it for a spin too if you really want. this relies on Psych internals, so it has a dependency on pysch ~> 2.0. it might work fine with other versions; that's just all i've tested it against at the moment.

cnuregexp allows tags to be placed inside a regex which function as labels for the matches. The matches within the MatchData object can then be accessed like a hash with the tag name as the key. cnuregexp also provides a greedy match which will return an array of all matches rather than just the first match. cnuregexp can also extract various data from an xml tag with the Regexp.xml_tag method. It uses Regexps to get the tag name, the attributes and their values, the tag content, and any other relevant data from an xml string. Lastly, cnuregexp allows commonly used regular expressions to be stored in a config file(lib/cnuregexp_config.yml) and accessed with Regexp.regular_expression_name notation eg. Regexp.ssn, Regexp.email_address. cnuregexp comes preloaded with a few common regular expressions which are located in lib/cnuregexp_config.yml.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.