Generate custom and random unique strings
Custom unique ID generator with prefix and sequential numbering
Generate custom, unique, random alphanumeric IDs.
Generate a unique character string suitible for use in files and URLs.
Generate unique and memorable names
mongoose-unique-validator is a plugin which adds pre-save validation for unique fields within a Mongoose schema.
Generate a unique random string
Generate a unique filename for use in temporary directories or caches.
Deconstructs and generates snowflake IDs using BigInts
Ensure CSS selectors are unique.
Generate unique and memorable names
Remove duplicate values from an array. Fastest ES5 implementation.
A universally-unique, lexicographically-sortable, identifier generator
Generate random or sequential UUID of any length
A module to create a set of unique numbers as fast as possible.
Given a DOM node, return a unique CSS selector matching only that element
Amazingly short non-sequential url-friendly unique id generator.
node.js through stream that emits a unique stream of objects based on criteria
Tiny but linear growing unique id generator
unique id extension for tiptap
A package to generate a unique username from email or randomly selected nouns and adjectives. User can add a separator between the username, define the maximum length of a username and adds up to six random digits.
取得陣列唯一值，支援深度比較巢狀物件和陣列 / Get unique values from array with deep comparison for nested objects and arrays
Header anchors for markdown-it.
Unique tag for use in the type-fest Tagged type
Hansel is a custom logger for making it simpler to attach a unique transaction ID (UTID) to all log messages.
Sequel Model plugin that adds [0-9a-z] unique id prefixed by a custom string.
Adds custom handling for database uniqueness constraints to ActiveRecord.
A common example is comparing customer lists between businesses, e.g., hashed unique email domains for users
Bond is on a mission to improve autocompletion in ruby, especially for irb/ripl. Aside from doing everything irb's can do and fixing its quirks, Bond can autocomplete argument(s) to methods, uniquely completing per module, per method and per argument. Bond brings ruby autocompletion closer to bash/zsh as it provides a configuration system and a DSL for creating custom completions and completion rules. With this configuration system, users can customize their autocompletions and share it with others. Bond can also load completions that ship with gems. Bond is able to offer more than irb's completion since it uses the full line of input when completing as opposed to irb's last-word approach.
This gem allows you to copy your static assets to include a unique hash in their filename. By using this and modifying your Rails asset path you can easily enable your Rails application to serve static content using CloudFront with a custom origin policy.
MobilityUniqueness extends the Mobility gem with locale-specific uniqueness validation for translated attributes in ActiveRecord models. It allows you to ensure that a given attribute, such as `name` in different locales, is unique within the specified locale. By using this validator, you can enforce uniqueness for translations without needing to write complex custom validation code in your Rails models. The gem works seamlessly with Mobility’s `KeyValue` backend to query translations and check for duplicates.
Some projects are confined by regulations (or requirements) that demand data can not be used to identify individuals. In such cases data must be scrubbed i.e. identifiable object names must be removed before unauthorized users can see said data. For example, when a developer needs to recreate a bug on their own system that was reported by a customer using customer-specific data. One method to do this is to use globally unique identifiers within the system to identify any given object.
This gem (spree extension) provides support for multiple suppliers in one store. Products should be assigned to the supplier that they belong to, which allows you to select a supplier and view only their products. Suppliers can be associated with Taxons that allow the customer to search for suppliers by taxon. Orders are also broken up into supplier invoices (one for each different supplier in the order), which list only the products that were purchased from that supplier. A mailer is in place to send each supplier their unique invoice descrbing what products they have sold and to who. The spree order mailer has also been modified to show all of the supplier invoices to the customer, along with the standard spree order number and info. The checkout process is combined so the customer only makes one transaction - the transaction can then be divided up amongst the suppliers involved in the transaction, according to the supplier_invoices. There is also an option for the site administrator to charge a percentage fee on each transaction to suppliers (this is currently set to 0%, but can be changed).
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
CustomId generates unique, human-readable, prefixed string IDs (e.g. "usr_7xKmN2pQ…") for ActiveRecord models. Inspired by Stripe-style identifiers. Supports embedding shared characters from related model IDs, custom target columns, configurable random-part length, and an optional PostgreSQL trigger-based alternative.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
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.