please check out the improved ramda repl: http://ramdajs.com/repl/
thanks to @craigdallimore for all the improvements
thanks to @craigdallimore for all the improvements
@buzzdecafe also will be better use
Run button on demand.
everyone's a critic :smile:
@buzzdecafe Also really slooowww
@buzzdecafe
Error: Failed to load http://wzrd.in/standalone/sanctuary@latest
hmmmm
the graceful failure is an improvement
but will look into the slowness. although nothing fundamental about how it evaluates has changed
merely how it loads on the page
slowness may be a side-effect of wzrd failing to serve sanctuary and RF
sigh
@ram-bot
Promise.resolve(10).then(x => console.log(x));
Promise { <pending> }
I like a monadic catamorphism :smile: https://goo.gl/m8e9SI
Hi there! Is there any way to build array from function arguments using Ramda?
Something like
var fn = function(){ return Array.from(arguments) }
Oh, I've found
R.unapply(R.identity)
@stepankuzmin you don't need to use
Array.from just spread const fn => (...args) => args.map(x => x * 10)
Thanks @xgrommx!
Kinda lost on re-arranging this one
const update = todo => {
//:: String -> Either a b
id = toObjectId(todo._id);
//->_Right { value: '580a86e0ccb07e6a515f1244' }
return new Future((reject, resolve) => {
collection.updateOne({_id: id}, {$set:{done: todo.done}})
.then(data => resolve(data))
.catch(err => reject(err));
});
};
It would help to split up things into functions first, then see where your types are at.
//getId:: todo -> Either e ObjectId
const getId = compose(toObjectId, prop('_id'));
//updateTodo :: ObjectId -> Todo -> Future e mongoResult
const updateTodo = futurize((_id, todo) => collection.updateOne({_id}, {$set:{done: todo.done}})
Now we see we have a function that takes an ObjectId, but another that returns an Either
const update = (todo) => map(updateTodo(__, todo), getId(todo))
You end up with an
Either e (Future e MongoResult)
Potentially, you could aggregate errors by having
toObjectId return a Future instead of an Either (after all, they share the same basic shape)
Then you use
chain to flatten it
I was thinking about #2.
For some reason I couldn't get futurizeP to work yesterday.
You can always write a helper function:
const updateOne = curry((coll, query, updates) => Future((rej, res) => coll.updateOne(query, updates).then(res, rej)));
Ah. Should have done that first.
Do people commonly use Futures for not-async stuff?
Speaking for myself, I will if I need to mix async code with non-async but failable code
It depends if you want to keep the errors separate
You can also convert from an Either to a Future
That's for Maybe but the same idea applies