A tool that converts enums to string literal enum with only one click. Build with ❤️.
Strip comments and string literals from JavaScript code
micromark extension to support GFM autolink literals
mdast extension to parse and serialize GFM autolink literals
Object literal maintaining its properties in the order they were added
ESLint plugin for i18n
TypeScript Enum Utilities
Base functionality used throughout XY Labs TypeScript/JavaScript libraries
Parameterised tests for Jest
An encapsulated logger for semantically formatting console messages.
remark-lint rule to warn when URLs without angle brackets are used
No description provided.
Allow parsing of Decimal, Binary, Hex and Octal literals that contain a Numeric Literal Separator
Tagged template literal for Sanity.io GROQ-queries
Regular expression parser for ECMAScript.
A literal expression view for dmn-js
Static TypeScript types from a literal JSONSchema type
nlcst utility to check whether a node is meant literally
Turn JavaScript objects into their AST representation.
ECMAScript code generator
Just a reasonable typeof
An AST parser for ICU MessageFormat strings
TypeSpec Azure Core library
Translates between RDF literals and JavaScript primitives
Stop using integers in your database when using enums. Use the enum type define in your model for better DX.
A comprehensive Enum library for Ruby with literal-style syntax.
Rails support for Literal Enums.
A simple Gem to enable any `ActiveRecord::Base` object to store a set of attributes in a set like structure represented through a bitfield on the database level. You only have to specify the name of the set to hold the attributes in question an the rest is done for you through some fine selected Ruby magic. Here is a simple example of how you could use the gem: class Person < ActiveRecord::Base has_set :interests end To get this to work you need some additional work done first: 1. You need an unsigned 8-Byte integer column in your database to store the bitfield. It is expected that the column is named after the name of the set with the suffix `_bitfield` appended (e.g. `interests_bitfield`). You can change that default behavior by providing the option `:column_name` (e.g. `has_set :interests, :column_name => :my_custom_column`). 2. You need a class that provides the valid values to be stored within the set and map the single bits back to something meaningful. The class should be named after the name of the set (you can change this through the `:enum_class` option). This class could be seen as an enumeration and must implement the following simple interface: * There must be a class method `values` to return all valid enumerators in the defined enumeration. * Each enumerator must implement a `name` method to return a literal representation for identification. The literal must be of the type `String`. * Each enumerator must implement a `bitfield_index` method to return the exponent of the number 2 for calculation the position of this enumerator in the bitfield. **Attention** Changing this index afterwards will destroy your data integrity. Here is a simple example of how to implement such a enumeration type while using the the `renum` gem for simplicity. You are free to use anything else that matches the described interface. enum :Interests do attr_reader :bitfield_index Art(0) Golf(1) Sleeping(2) Drinking(3) Dating(4) Shopping(5) def init(bitfield_index) @bitfield_index = bitfield_index end end