Accessible, lightweight, unstyled implementations of UI patterns that still need runtime help.
List-related schema elements and commands for ProseMirror
Basic schema elements for ProseMirror
This package provides utilities for creating schema for different types, along with serialization information.
An ESLint plugin to raise awareness for using inclusive language not only in your codebase, but in life.
XML language support for the CodeMirror code editor
A Long class for representing a 64-bit two's-complement integer value.
A Long class for representing a 64-bit two's-complement integer value.
Treat React JSX elements as value types and hoist them to the highest scope
Editor state data structures for the CodeMirror code editor
Undo history for ProseMirror
ProseMirror editor state
Keymap plugin for ProseMirror
ProseMirror's view component
Linting support for the CodeMirror code editor
Search functionality for the CodeMirror code editor
Array manipulation, ordering, searching, summarizing, etc.
Editing commands for ProseMirror
Automatic transforms on text input for ProseMirror
List of HTML void tag names
a CSS selector compiler/engine
ProseMirror's document model
ProseMirror document transformations
Collaborative editing for ProseMirror
Provides short interface for choosing elements from array of structs. Filtering by equality, matching and inclusion, e.g.: target.choose(:street => "Main", :age => (24..30), :address => /Main/) Filtering by instance evaluated string, e.g.: target.choose("age >= 24 && address =~ /^Main/") Rejecting elements with #choose_not method, e.g.: target.choose_not(:street => "Main")
RJS is a great Ruby DSL to write javascript. However, it's so tempting to write RJS directly in the views, and soon the views contain substantial controller knowledge (e.g. link_to_remote, link_to, etc) KRJS attempts to solve that problem by allowing dynamic inclusion of AJAX calls on HTML elements. When a controller defines a method (based on naming convention) that handles a client-side event, the rendering engine will do the wiring automatically - when the event happens, an AJAX call will be made to the controller's method which would ideally reply with RJS and update portions of the document.
RJS is a great Ruby DSL to write javascript. However, it's so tempting to write RJS directly in the views, and soon the views contain substantial controller knowledge (e.g. link_to_remote, link_to, etc) KRJS attempts to solve that problem by allowing dynamic inclusion of AJAX calls on HTML elements. When a controller defines a method (based on naming convention) that handles a client-side event, the rendering engine will do the wiring automatically - when the event happens, an AJAX call will be made to the controller's method which would ideally reply with RJS and update portions of the document.