Vanilla implementaion at humps

• use sideEffects: false
• trace why the es distribution does break tree-shaking
• create sample repo with R_ and Webpack for easy debugging and experimenting

Example in trace is not working out of the box.

Based on cglane's ramda/ramda#2497

between(0, 1, 2) // 2 not in [0, 1] =>  false
between(0, 2, 1) // 1 is in [0, 1] => true

dispatch is great, but sometimes R.isNil is not desirable... see:

const getFirstBirthNumber = path([0, 'birthNumber']);

const getBirthNumber = R_.dispatch([
  o(when(complement(Boolean), R_.noop), R_.headArg),
  compose(getFirstBirthNumber, R_.lastArg)
])

getBirthNumber("x", [{ contract: { birthNumber: "s" } }])

with something like dispatchWith, can be example above simplified to:

const getFirstBirthNumber =path([0,  'birthNumber']);
const firstTruthy = R_.dispatchWith(complement(Boolean));

const getBirthNumber = firstTruthy([R_.headArg, compose(getFirstBirthNumber, R_.lastArg)])

getBirthNumber("x", [{ contract: { birthNumber: "s" } }])

For example:

• defaultToNull
• defaultToFalse
• defaultToTrue
• defaultToEmptyObject
• defaultToEmptyArray
• defaultToEmptyString
• defaultToZero
• defaultToOne

Did I missed something?

I suggest renaming this function for consistency. (To be completely honest, I wouldn't use this function just because of its name :X).

same functionality as library classname

:) no description needed

fork this plugin https://www.npmjs.com/package/babel-plugin-ramda-patch. And make it work for ramda-extension

Output from alwaysEmptyArray and alwaysEmptyObject cannot be trusted to be always empty. Specially if their outputs are being passed around as inputs to third party libraries. This can lead to hard to track bugs and odd behaviors.

R_.alwaysEmptyArray(); // []
R_.alwaysEmptyArray().push(42); 
R_.alwaysEmptyArray(); // [42] <- return value has been changed forever for every other subsequent call

I propose we either:

• Change the name of the functions to reflect the above fact.
• Return a R.clone of the emptyArray or emptyObject each time:

const alwaysEmptyArray = () => clone(emptyArray);

• Leverage the new (unreleased as of yet) R.thunkify function to create a point-free reusable factory of clones and implement other always* functions based off of it.

const alwaysNew = thunkify(clone);
const alwaysEmptyArray = alwaysNew(emptyArray);

DISCLAIMER: I was the author of the thunkify PR.

http://ramdajs.com/repl/?v=0.25.0#?const%20padLeftUntil%20%3D%20useWith%28until%2C%20%5Bidentity%2C%20concat%2C%20toString%5D%29%3B%0Aconst%20myPad%20%3D%20padLeftUntil%28x%20%3D%3E%20x.length%20%3E%2010%2C%20%270%27%29%20%0A%0AmyPad%28111%29%3B

Do you think it is useful? @jbradle @aizerin @lukasduspiva @wafflepie @neerajdotname

See @nfantone`s comment.

See startsWithSuffixIgnoreCase function.

Hello,

we use cx as a replacement of classNames lib.

But unfortunatelly it produces final classnames with more spaces than necessary.
For example:

R_.cx(['Table', 'MagicTable '])    // "Table MagicTable "
R_.cx(['Table', '    MagicTable']) // "Table     MagicTable"
R_.cx([' Table', 'MagicTable'])    // " Table MagicTable"

It would be nice if cx remove unnecessary spaces, isn't it?

const ref = { current: null };
const getRef = always(ref);
const createRef = (current) => ({ current });

applyIfFunction(ref, []); // { current: null }
applyIfFunction(getRef, []); // { current: null }
applyIfFunction(createRef, [document.body]); // {"current": [object HTMLBodyElement]}

callIfFunction(ref) // { current: null }
callIfFunction(getRef) // { current: null }
callIfFunction(createRef, document.body) // {"current": [object HTMLBodyElement]}

I ofter use the function in React components.
Sometimes a property is either function (then you need to call it) or just static value.

Support es and commonjs modules. We can do it same as ramda.

same functionality as keymirror library

Refactor camelizeKeys into implementation with mapKeysAndValues.

Allow to show ramda functions in online documentation.

Add TS dictionary to @types

Fork ramda docs and use it same way for the ramda-extension.

must be compatible with github pages.

npm/www#329

Instead of

https://github.com/tommmyy/ramda-extension/tree/0.3.0/packages/ramda-extension/src/isNilOrEmptyString.js

there is:

https://github.com/tommmyy/ramda-extension/tree/0.3.0/src/isNilOrEmptyString.js

Looks cool: https://github.com/rung-tools/eslint-plugin-ramda

it would be nice to have a fulltext search function that is able to search according to given string value in the array of objects values.

And it would be even nicer if that search function could search through an array of deeply nested objects.

Example:
input array:
[
{
"id": 1,
"name": "Exposure time",
"description": "Possible exposure times",
"type": "text",
"language": "en",
"attributes": {
"min": "1/1000 sec",
"max": "30 sec"
},
},
{
"id": 2,
"name": "Durability",
"description": "Durable material",
"type": "text",
"language": "en"
},
{
"id": 3,
"name": "Stabilizer",
"description": "Stabilizer enabled",
"type": "boolean",
"language": "en"
}
]

search string: "sec"
result:
[
{
"id": 1,
"name": "Exposure time",
"description": "Possible exposure times",
"type": "text",
"language": "en",
"attributes": {
"min": "1/1000 sec",
"max": "30 sec"
},
}
]

https://github.com/tommmyy/ramda-extension/community

Otherwise they won't live up to their promise of being always empty.

Proof of concept