Comparing version 0.7.0 to 0.7.1
{ | ||
"name": "absurdum", | ||
"version": "0.7.0", | ||
"version": "0.7.1", | ||
"description": "Reductio Ad Absurdum - The Riduculous Application of Reduce", | ||
@@ -5,0 +5,0 @@ "keywords": [ |
@@ -20,31 +20,2 @@ [![npm](https://img.shields.io/npm/v/absurdum.svg)](https://www.npmjs.com/package/absurdum) | ||
## Rules of Engagement | ||
Before I introduce the steps to begin, let's set some ground rules. You can implement an operator for anything you'd like but there are a few constraints. | ||
1. You must use reduce in your solution, no map/filter/foreach | ||
2. Your solution must be functional, with no side-effects | ||
3. Recursion will be allowed for nested data types | ||
4. If recursion is used, it must be tail call optimized | ||
5. Be mindful of performance | ||
6. Use only vanilla JS, whatever features babel-preset-env supports | ||
## Getting Started | ||
This library is designed to make contributing as easy and simple as possible. | ||
Start by suggesting a new [Operator][operator] or [Type][type]. | ||
Development is done following the [Feature Branch Workflow][feature-workflow]: | ||
1. Fork the repo | ||
2. Clone your fork | ||
3. Create a *feature branch* named after your operator | ||
4. Run `npm run start`, so webpack can watch for changes | ||
5. Implement your operator | ||
6. Add a test to verify its functionality | ||
7. Add supporting documentation | ||
8. Cleanup with 'npm run lint' | ||
8. Submit a PR | ||
## Operator(s) Documentation | ||
@@ -51,0 +22,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
34969
19
32
56