Keep your for loop syntax the same for all different types.
Just pass in your constraints and callback and we will determine best course of action.
If you pass in anything with a value(obj, map, arr), you will always get that returned first otherwise it will be the iterator or key. Please see examples below
$ npm install 4loop
const fourLoop = ;const obj = foo: 'bar' baz: 'cat' ;const arr = 'foo' 'bar' 'baz' 'cat';const arrLength = arrlength;const mySet = 'foo' 'bar' baz: 'cats' ;const myMap = 'foo' 'bar' 'baz' 'cats' 'dogs' undefined;;;;;;
Developing and contributing to 4loop
The main body of code is in
The tests are in the
test/spec directory. Please follow naming convention with
We use Feather-test which is similar to jasmine for unit tests. Unless there is a very compelling reason to use something different, please continue using Feather for tests. The existing tests are in the spec folder. Here are some useful command shortcuts:
Run all the tests:
Run only some tests:
npm test --run=nameOfFile
Before submitting a pull request
Please make sure all code supports all versions of node.
We use ESLint for syntax consistency, and the linting rules are included in this repository. Running
npm test will check the linting rules as well. Please make sure your code has no linting errors before submitting a pull request.
eslint . --fix will also automatically fix any linting errors.