Results for reduce-keys

Get Refile URL from key using SHA.

Blazingly fast recursive convertion to and from camelCase or PascalCase for Objects and Arrays

reduce an object

Reduce transform functions with PostCSS.

Constants and utilities about visitor keys to traverse AST.

Isomorphic map-reduce function to flatten an array into the supplied array

Reduce initial definitions to the actual initial value, where possible.

Compile objects with duplicate keys to valid strict ES5

Reduce CSS calc() function to the maximum

Reduce function calls in a string, using a callback

Visitor keys used to help traverse the TypeScript-ESTree AST

An Object.keys replacement, in case Object.keys is not available. From https://github.com/es-shims/es5-shim

Robustly get an object's own property keys (strings and symbols), including non-enumerables when possible

Reduce a list of values using promises into a promise for a value

Reduce custom identifiers with PostCSS.

Reduce multiple reducers into a single reducer

Types for the TypeScript-ESTree AST spec

A best-practices CSS foundation

High quality image resizing for blobs in browsers (`pica` wrapper with some sugar)

`[].reduce()` for old browsers

Reduce any JSON value by traversing depth first and visiting each node

Safe defaults for cssnano which require minimal configuration.

Utility for creating Universal macOS applications from two x64 and arm64 Electron applications

No description provided.

High speed data aggregator and reducer algorithm based on key-value exact matching and grouping.

Blazy(be lazy) is a fluent extension to active record models to reduce number of key strokes in rails console

Helping Ruby developers and their companies, unlock their key-value store data, through associative and sequential based access, providing unprecedented support for map reduce behaviors, native to the Ruby language

A Sinatra extension for setting and showing Rails-like flash messages. This extension improves on the Rack::Flash gem by being simpler to use, providing a full range of hash operations (including iterating through various flash keys, testing the size of the hash, etc.), and offering a 'styled_flash' view helper to render the entire flash hash with sensible CSS classes. The downside is reduced flexibility -- these methods will *only* work in Sinatra.

Configures Rails to load credentials master and environment key files from an out-of-band location (XDG on Linux/macOS, AppData on Windows) instead of the project directory. This reduces the risk of key exposure from tooling that reads or executes within your repo, including modern AI assistants and agentic tools.

The Database Center API provides access to an organization-wide, cross-product database fleet health platform. It aggregates health, security, and compliance signals from various Google Cloud databases, offering a single pane of glass to identify and manage issues. Note that google-cloud-database_center-v1beta is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-database_center instead. See the readme for more details.

The Database Center API provides access to an organization-wide, cross-product database fleet health platform. It aggregates health, security, and compliance signals from various Google Cloud databases, offering a single pane of glass to identify and manage issues.

A Sinatra extension for setting and showing Rails-like flash messages. This extension improves on the Rack::Flash gem by being simpler to use, providing a full range of hash operations (including iterating through various flash keys, testing the size of the hash, etc.), and offering a 'styled_flash' view helper to render the entire flash hash with sensible CSS classes. The downside is reduced flexibility -- these methods will *only* work in Sinatra.

Use Mysql AUTO_INCREMENT to support key value cache, which should be combined by an integer and string. It means to reduce the database storage size, and improve query performance. All cache will store in process memory, and will never be expired, until the process dies, so the less kvs you use, the better performance you will get. BTW, 100,000 general strings use 10MB memory. Some relatived articles: http://en.wikipedia.org/wiki/Correlation_database Usage ------------------------------------------ ## setup ```ruby create_table :kv_browser_names, :options => 'ENGINE=MyISAM DEFAULT CHARSET=utf8' do |t| t.string :name t.timestamps end class KvBrowserName < ActiveRecord::Base include IdNameCache end ``` or ```ruby create_table :common_tag, :options => 'ENGINE=MyISAM DEFAULT CHARSET=utf8' do |t| t.integer :tagid t.string :tagname end class CommonTag < ActiveRecord::Base self.table_name = :common_tag self.primary_key = :tagid include IdNameCache; set_key_value :tagid, :tagname # include IdNameCache; set_key_value_without_create :tagid, :tagname # if you dont want create it automately end ``` ### use cases ```text ruby-1.9.3-rc1 :001 > QuizTag[1] QuizTag Load (0.3ms) SELECT `common_tag`.* FROM `common_tag` WHERE `common_tag`.`tagid` = 1 LIMIT 1 => "Android" ruby-1.9.3-rc1 :002 > QuizTag[1] => "Android" ruby-1.9.3-rc1 :003 > QuizTag['Android'] QuizTag Load (0.5ms) SELECT `common_tag`.* FROM `common_tag` WHERE `common_tag`.`tagname` = 'Android' LIMIT 1 => 1 ruby-1.9.3-rc1 :004 > QuizTag['Android'] => 1 ``` == Copyright MIT, David Chen at eoe.cn

Have you ever wanted to call &lt;code&gt;exit()&lt;/code&gt; with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across &lt;code&gt;sysexits(3)&lt;/code&gt;. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about &lt;code&gt;style(9)&lt;/code&gt; as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, &lt;code&gt;exit(1)&lt;/code&gt; is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at &lt;code&gt;Sysexits::EX__BASE&lt;/code&gt; (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via &lt;code&gt;include Sysexits&lt;/code&gt;, or as &lt;code&gt;Sysexits::STATUS_CODES&lt;/code&gt;, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're &lt;em&gt;building a totally-awesome future in the Cloud™!&lt;/em&gt; include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used &lt;code&gt;fork()&lt;/code&gt; more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.