Issue with find: doesn't flow about npm-ramda HOT 4 CLOSED

The same problem actually with other methods:

let obj: { id: number } = { id: 1 }
R.prop<string>('id')(obj)

And in general I believe that is some limitation of TS. In this cases it is more appropriate to use not ramda but simple mapping function like (_) => _.id that will flow perfectly.

Ok this will flow:

let obj: { id: number } = { id: 1 }
R.prop('id')<string>(obj)

But how to use it with for example R.compose to get correct flow?

let obj: { id: number } = { id: 1 }
R.compose(R.prop('id')<string>)(obj) // this won't work

What do you think?

from npm-ramda.

I changed the definition of the curried find to:
find<T>(fn: (a: T) => boolean): <T>(list: T[]) => T;
and now it works as expected, see pr #91

from npm-ramda.

Concerning the 'prop'-issue. This is a know limitiation of TS. Version 1.8+ should fix that, see #10

from npm-ramda.

@donnut

Concerning the 'prop'-issue. This is a know limitiation of TS. Version 1.8+ should fix that, see #10

I'm using 2.1-dev. What signature are you talking about? It seem that string based typing is not supported.

from npm-ramda.