A global utility for tracking the current input method (mouse, keyboard or touch).
Ember CLI wrapper for what-input
React hook for what-input integration
A PostCSS plugin used to make it easy to interact with the npm module "what-input".
debugging broccoli plugin to log if and what input changed
remark plugin to add support for serializing markdown
natural language processor powered by plugins part of the unified collective
TypeScript-first schema declaration and validation library with static type inference
remark plugin to add support for parsing markdown input
A parser for the TypeScript doc comment syntax
Type checking for JavaScript functions
`trough` is middleware
a glob matcher in javascript
Telephone number input React component
Virtual file format.
mdast utility to parse markdown
read(1) for node programs
rehype plugin to format HTML
RE2JS is the JavaScript port of RE2, a regular expression engine that provides linear time matching
rehype plugin to serialize HTML
hast utility to create a tree from the DOM
Sanity input component for code, powered by CodeMirror
retext plugin to serialize prose
A tool to migrate a template from MJML 3 to MJML 4
Decide what to have for lunch today, based on a number of inputs
TypeProf performs a type analysis of non-annotated Ruby code. It abstractly executes input Ruby code in a level of types instead of values, gathers what types are passed to and returned by methods, and prints the analysis result in RBS format, a standard type description format for Ruby 3.0.
Infer from the HTML5 input whether it's a fragment or a document, and if it's a fragment what the proper context node should be. This is useful for parsing trusted content like view snippets, particularly for morphing cases like StimulusReflex.
Interactors are a pattern for structuring your business logic into units. They have a flexible context that they pass between them, which makes them easy-to-write, but hard-to-understand after you've written them. Much of this confusion comes from not knowing what the interactor is supposed to take as input and what it's expected to produce. Enter contracts. Contracts allow you define, up front, a contract both for the input of an interactor, known as expectations, and the output of it, known as promises. Additionally, you can define a handler for what happens when an interactor violates its contracts, known as a breach. Declaring these contracts can help define your interface and make it easier to understand how to use an interactor. They form both documentation and validation for your business logic.
users get prompted for an input and the gem outputs the user inputs. This is just a test though. you can pick it up and modify it to what ever you want. Have fun with it :)
Send and receive data via a Web App's API, ideally using WatirModel objects. The goal is to compare test data with what is input and displayed via UI.
Services help keep your business logic clean, but what helps keep your services clean? Civil provides a framework for writing services that all have a standardized structure, inputs and outputs.
Send and receive data via a Web App's API, ideally using WatirModel objects. The goal is to compare test data with what is input and displayed via UI.
Miniparser works pretty simply. You pass the Gem some input (HTML, JS, or CSS), and it will validate it, return the validated status, then minify it, and return the minified version as either a file (path) and a text return, respective to what input it got
RbbCode is a customizable Ruby library for parsing BB Code. RbbCode validates and cleans input. It supports customizable schemas so you can set rules about what tags are allowed where. The default rules are designed to ensure valid HTML output.
Belletrist is a collection of Ruby DSLs for generation of different data file types. Currently, HTML and JSON are supported but that will grow as my needs do, or if other people want or contribute any other DSLs. It is important to note that Belletrist has a focus on performance, not correctness. Belletrist ascribes to the rule of "what goes in, must come out", and as such Belletrist DSLs must output well-formed documents so long as the developer provides Belletrist valid input. If that contract is broken the result is undefined.
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace
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.
No description provided.
No description provided.
No description provided.