Results for army-negative

Is this value negative zero? === will lie to you

traverse and transform objects by visiting every node on a recursive walk

The Swiss Army Knife of Vector Graphics Scripting

Test if a double-precision floating-point numeric value is negative zero.

Resolver for git-hosted packages

二重否定をチェックするtextlint rule

A function that tells you whether a given element is overflowing its container or not. Useful for creating dropdowns and tooltips.

A tiny, PEG-like system for building language grammars with regexes.

Returns an array of all tabbable DOM nodes within a containing node.

Check if something is a negative number

Fast robust predicates for computational geometry

The Swiss Army Knife of Vector Graphics Scripting, packaged for headless use in Node.js

Negative binomial distributed pseudorandom numbers.

Tailwind CSS plugin, add animation-delay CSS property.

deconstruct a number format eg '-£#,##0.##0' and return a set of parameters to describe the format

Test if a finite double-precision floating-point number is a negative integer.

Calculates the distance from a point to the edges of a polygon or multi-polygon.

Make a glob pattern absolute, ensuring that negative globs and patterns with trailing slashes are correctly handled.

efficiently store signed integers in varint

The Cyber Swiss Army Knife for encryption, encoding, compression and data analysis.

Generate one or more common English words

io-ts library for bigints

Creates a buffer around a GeoJSON feature.

Double-precision floating-point negative infinity.

When this gem is loaded and activated inside your rails app, your MySQL connection adapter for ActiveRecord will be monkey-patched. The patch simply tweaks it to store all boolean "true" values as negative one instead of positive one inside your TINYINT columns. It also patches it to recognize and interpret negative one as "true". Positive one will still be recognized as true as well. Used for special cases, such as developing rails apps that must, for example, work with existing databases that use such a convention. For a rails app version X.Y.Z, use army-negative version "~> X.Y.0". For example, a rails 3.0.x app should use "~> 3.0.0" and a 3.1.x app would use "~> 3.1.0", etc. The exception is that rails 2.3.x apps should just use "~> 2.0" since 2.3 is the earliest version of rails that's supported.