These are chat archives for ramda/ramda

10th
May 2018
Stephen Niemans
@stephenniemans
May 10 2018 08:49
@nateabele I am, though pretty new to this all :) What are you running into?
Waqas Noor
@waqasnoor
May 10 2018 10:57
@ram-bot
const obj = { a: 'a', actions: [{ name: '1' }, { name: '2' }] };
const lens = lensPath(['actions', 1, 'name']);
view(lens)(obj);
set(lens, 5, obj);
Nate Abele
@nateabele
May 10 2018 13:37
@stephenniemans Trying to figure out what types package to use. There doesn't seem to be consensus on whether to use types/npm-ramda or @types/ramda, but they both seem to have (different) issues.
Stephen Niemans
@stephenniemans
May 10 2018 13:44
@nateabele I'm personally using @types/ramda, I've not run into issues yet and it was pretty easy to setup. That said, my usage is pretty limited and you might run into trouble when you start doing more advanced stuff?
Nate Abele
@nateabele
May 10 2018 13:45
Yeah, we use it pretty extensively.
Stephen Niemans
@stephenniemans
May 10 2018 13:50
Ah, then I likely can't teach you much ;) I'd be interested to hear what you discover, however - just started looking more deeply into it myself!
Stephen Niemans
@stephenniemans
May 10 2018 21:08
@nateabele having a go with types/npm-ramda atm, the @types/ramda package started giving me problems quite soon after we spoke (example, R.path not accepting an array of strings as param). So far not run into anything too crazy yet, what caveats have you run into with it?