Observed since 20 Oct, 20:12 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
4loop
Standard ForLoop syntax. Keep syntax clean and standard no matter what you pass us (arrs, objs, maps,etc.
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 = require('4loop');
const obj = { foo: 'bar', baz: 'cat' };
const arr = ['foo', 'bar', 'baz', 'cat'];
const arrLength = arr.length;
const mySet = new Set(['foo', 'bar', { baz: 'cats' }]);
const myMap = new Map([['foo', 'bar'], ['baz', 'cats'], ['dogs', undefined]]);
fourLoop(obj, (value, key, iterator) => {
// Do magic here
if (iterator === 1) {
console.log(value, key, iterator); // Prints cat, baz, 1
}
});
fourLoop(arr, (value, key, iterator) => {
// Do magic here
if (iterator === 1) {
console.log(value, key, iterator); // Prints bar, bar, 1
}
});
fourLoop(arrLength, (value, key, iterator) => {
// Do magic here
if (iterator === 1) {
console.log(value, key, iterator); // Prints 1, 1, 1
}
});
fourLoop(mySet, (value, key, iterator) => {
// Do magic here
if (iterator === 1) {
console.log(value, key, iterator); // Prints bar, bar, 1
}
});
fourLoop(myMap, (value, key, iterator) => {
// Do magic here
if (iterator === 1) {
console.log(value, key, iterator); // Prints cats, baz, 1
}
});
The main body of code is in index.js.
The tests are in the test/spec directory. Please follow naming convention with xxxx.spec.js
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:
npm test
npm test --run=nameOfFile
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.
Download counts and popularity will appear here as the collector receives them.
| Package / target | Requirement | Relationship |
|---|---|---|
babel-eslintEnvironment{
"local_name": "babel-eslint",
"alias": false,
"peer_metadata": null
} | ^8.0.1 | development |
eslint-config-airbnb-es5Environment{
"local_name": "eslint-config-airbnb-es5",
"alias": false,
"peer_metadata": null
} | ^1.2.0 | development |
eslint-plugin-reactEnvironment{
"local_name": "eslint-plugin-react",
"alias": false,
"peer_metadata": null
} | ^7.4.0 | development |
feather-testEnvironment{
"local_name": "feather-test",
"alias": false,
"peer_metadata": null
} | ^3.3.0 | development |
Source distribution
{
"shasum": "9d51c000006b214b76fc53553b5a3a6e5738080f",
"tarball": "https://registry.npmjs.org/4loop/-/4loop-1.1.5.tgz",
"integrity": "sha512-m9g7+9GI9QOWo0qZw3Obj+RvYEyyTbSA6ygMzwIgCN2434DlbxI0mE9EH5lXKAVanhRfuhqP+1opPCGFIdbgQA==",
"signatures": [
{
"keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
"sig": "MEQCIDlsSnWatdc/NdmIdcKcE9LE3C2VOafdIJN5R1tofFaAAiArJhJ60ll/e60CDgh8eYj7NeCQKAJ5F22PZRLAq7t5Ig=="
}
]
}Observed since 20 Oct, 20:12 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package_version:5cddaafe7abe469d638e5f72ff3882f80f8142cec72b09d3530cd0aa4ec4d06d