Spread out all of the possibilities, given an object with iterable values
In probability theory and statistics, variance measures how far a set of numbers is spread out. http://en.wikipedia.org/wiki/Variance
Compile object rest and spread to ES5
Compile ES2015 spread to ES5
Allow parsing of object rest/spread
Transform optional chaining operators to workaround https://crbug.com/v8/11558
Easily handle defaults for your options
micromark extension to support MDX or MDX JS expressions
An exhibition of digital artworks installed on Wi-Fi routers spread out in the public space
Allow parsing of object rest/spread
A JavaScript library for efficient immutable updates
Compile ES2015 spread to ES5
Wrap a controlled react component, to allow specific prop/handler pairs to be uncontrolled
Support object spread in acorn
ESLint rule for suggesting that object spread properties be used instead of Object.assign().
SpreadJS Designer Component present as a control that could be embedded into your web application easily, and also provided flexible, customizable configuration to achieve your business logic.
Compile object rest and spread to ES5
The Spread physics simulation layout for Cytoscape.js
A Complete Microsoft Excel-like JavaScript Spreadsheet for Enterprise Applications
🐊Putout plugin adds ability to remove useless spread
🐊Putout plugin adds ability to remove useless spread
🐊Putout plugin adds ability to convert 'apply' to 'spread'
Post compiler for Vue template render functions to support ES2015+ features
Webpack loader for Sucrase
Tiny, ergonomic Discord Rich Presence library for your Rust apps.
A fast, interactive TUI for exploring and running Makefile targets
Spread lists with a CreamCheese::Knife, and put spacers in to even things out. `Knife.spread([list], length, [spacer (default=nil)])`
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.