-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with find: doesn't flow #88
Comments
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 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? |
I changed the definition of the curried find to: |
Concerning the 'prop'-issue. This is a know limitiation of TS. Version 1.8+ should fix that, see #10 |
Is it possible to make it flow in second case?
The text was updated successfully, but these errors were encountered: