@vtex/npm-ramda
v0.23.0-RC1
Published
[![Build Status](https://travis-ci.org/types/npm-ramda.svg?branch=master)](https://travis-ci.org/types/npm-ramda) [![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/donnut/typescript-ramda?utm_source=badge&utm_medium=badge&utm_campaign=
Downloads
3
Maintainers
Keywords
Readme
##Type definitions for Ramda
![Gitter](https://badges.gitter.im/Join Chat.svg)
Testing:
# old way, easy
npm test
# without npm
./node_modules/typescript/bin/tsc --lib \"es2015\" --module commonjs test.ts --noEmit
# diffing, more detailed, with npm
npm run diff
# without
ts-node typecheck.ts test.ts 2>&1 | tee typecheck.txt
Pull requests are welcome!
##Usage
Install the typings for node using:
npm install @types/ramda --saveDev
If you use the package through a script tag, use:
npm install @types/ramda --saveDev --global
##Note on placeholders
Due to incompatiblity problems with typescript's typing system, Ramda's placeholder
typing is removed. For binary functions the same functionally can be achieved using
R.flip
. For example:
// using a placeholder ...
R.subtract(*placeholder*, 3);
// ... is the same as
R.flip(R.subtract)(3);
In Ramda almost all functions are curried. TypeScript does not natively support currying, so in cases where we've omitted a combination this might break. Example of a potential gap:
R.insert(2, 'x', [1,2,3,4])
R.insert(2)('x', [1,2,3,4])
R.insert(2, 'x')([1,2,3,4])
R.insert(2)('x')([1,2,3,4]) // => type error!
##Status Typing compatible with ramda version 0.22.1.
##Testing
- unix:
npm test
- windows:
tsc --lib es2015 --module commonjs test.ts --noEmit
##Todo
- compose: use like extend rather than forcing types to be the same?
- Curry?
- issue: allow separating manual/inferred generics to allow providing hints to e.g. pipe/compose