These are chat archives for ramda/ramda

2nd
Apr 2015
Raine Virta
@raine
Apr 02 2015 07:30
nice. i like devdocs.io, which unfortunately doesn't have ramda documentation yet
Raine Virta
@raine
Apr 02 2015 12:24
naively i thought that creating non-mutable version of _.merge would be as simple as partially applying with an object
Scott Sauyet
@CrossEye
Apr 02 2015 12:42
:smile: been caught by that too.
Walle Cyril
@GrosSacASac
Apr 02 2015 15:19
what is the easiest way to call all function in a list in Ramda ?(order does not matter, function take no parameter)
Raine Virta
@raine
Apr 02 2015 15:41
sounds like ap
Raine Virta
@raine
Apr 02 2015 15:47
or R.forEach(R.call, fns) if one wants to make side-effecty result obvious
Nate Abele
@nateabele
Apr 02 2015 18:20
@raine: Found this channel via Google when searching for "Ramda cookbook" -- love the idea and would be happy to contribute.
Also, is anybody else writing ES6? I'm able to do import { is, map, keys } from "ramda"; which is very elegant and pretty, but requires some background hacks to export individual values from R.
Raine Virta
@raine
Apr 02 2015 19:13
@nateabele say that again when need 20 fns in a single file. it becomes very inelegant and pain in the ass :grin:
Nate Abele
@nateabele
Apr 02 2015 19:14
@raine Nope, still pretty elegant with line breaks -- the real value comes in the form of not littering my code with R. all over the place.
Raine Virta
@raine
Apr 02 2015 19:15
i wonder if there could be a mechanism for importing all without bad consequences, a macro or something
i dont think it's elegant to maintain a list of functions in the top of every file, but i do think it's better than R. all over
Nate Abele
@nateabele
Apr 02 2015 19:18
@raine The logical conclusion of that statement is that all dependencies should be global. ;-) Explicit imports enable more effective static analysis + custom builds.
Raine Virta
@raine
Apr 02 2015 19:21
global to file