very fast mongoid compatible unique string ids
KeystoneJS MongoId Field Type
Conversion of JavaScript primitives to and from Buffer with binary order matching natural primitive order
KeystoneJS MongoId Field Type
Stylelint config for Property Sort Ordering based on the SMACSS methodology
Collation functions for PouchDB map/reduce
Comprehensive ESLint plugin for vanilla-extract with CSS property ordering, style validation, and best practices enforcement. Supports alphabetical, concentric and custom CSS ordering, auto-fixing, and zero-runtime safety.
A simple organizer for ordering hooks.
Transform TypeScript `const` enums
This library contains auto generated Mongo (Mongoose.js) models that correspond to the QDM (Quality Data Model) specification.
- Skip the execution phase and reduce server load by caching execution results in-memory. - Customize cache entry time to live based on fields and types within the execution result. - Automatically invalidate the cache based on mutation selection sets. -
Hooks for building lightweight, fast and extendable datagrids for React
Stylelint config for Property Sort Ordering based on the SMACSS methodology
Fela plugin to validate style objects
Expo module implementation of a parser based on https://httpwg.org/specs/rfc8941.html
A [pie](http://github.com/PieLabs/pie) choice component.
A sequential combine mediator
Decorate yargs content with chalk styles and figlet fonts
Parse binary files with a schema into nicely readable objects
Sort Sails/Express-style route addresses by inclusivity
comparison for sensible javascript objects
Fluid server services zookeeper client implementation
Neon order stylelint order config
This package contains utility functions and types to ease the use of instrumentation accross Envelop, Yoga, whatwg-node and Hive Gateway plugins.
mongoid-ordering makes it easy to keep your Mongoid documents in order.
Enables Mongoid models to track their position in list
An easy way to make Mongoid documents order-able by adding position field
Mongoid Origin query extensions for dynamic query generation
Ordering behavior for ActiveRecord models and Mongoid documents.
Preserve the order of the mongoid documents in a referenced one-to-many or many-to-many relationship.
Easily implement search forms and column ordering based on your models scopes. For Rails 3, compatible with ActiveRecord and Mongoid.
Mongoid Scribe
This library tracks historical changes for any document, including embedded ones. It achieves this by storing all history tracks in a single collection that you define. Embedded documents are referenced by storing an association path, which is an array of document_name and document_id fields starting from the top most parent document and down to the embedded document that should track history. Mongoid-history implements multi-user undo, which allows users to undo any history change in any order. Undoing a document also creates a new history track. This is great for auditing and preventing vandalism, but it is probably not suitable for use cases such as a wiki.
With treeoid, you can create tree-style hierarchies for Mongoid classes. Just "include Treeoid" and you're ready to roll. You get a "parent" accessor, a "children" array, plus a scope called "hierarchically" that spits everything out in hierarchical order - perfect for front end rendering.
In frustration of Mongoid::Versioning, I created this plugin for tracking historical changes for any document, including embedded ones. It achieves this by storing all history tracks in a single collection that you define. (See Usage for more details) Embedded documents are referenced by storing an association path, which is an array of document_name and document_id fields starting from the top most parent document and down to the embedded document that should track history. This plugin implements multi-user undo, which allows users to undo any history change in any order. Undoing a document also creates a new history track. This is great for auditing and preventing vandalism, but it is probably not suitable for use cases such as a wiki.
When you have a project in which you are not using Mongoid::Timestamps and you want to mock an object's creation time, you have to do some cumbersome operations in order to get those first 4 bytes of the ObjectId to represent the seconds since the Unix epoch that you want for that object. Particularly, if you want to have two objects with the same creation time, it would not suffice to generate the IDs via the BSON::ObjectId.from_time method, since it would yield the same ID for both objects, and you probably do not want them to be seen as the same object. This gem solves this little annoying issue by generating a unique ID for the given timestamp by using the other 8 bytes in ObjectId to generate the needed additional entropy.