Ramda declarations, destructuring imports

To grab the interface file I ran: flow-typed install ramda -f 0.26, then added a line to my .flowconfig to produce:

[libs]
decls
flow-typed/npm

I created a trivial test file…

/* @flow weak */
import { identity } from 'ramda'
console.log(identity(3))

And on type checking got…

handlers/scratch.js:3
  3: import { identity } from 'ramda'
              ^^^^^^^^ Named import from module `ramda`. This module has no named export called `identity`.

Looking at the file, it appears that all of the declarations are exported building up one class through mixins, which class is then the sole export. This, it seems, produces the frustrating result above. I can work around this by avoiding destructuring import:

import Ramda from 'ramda'
const { map, add, identity } = Ramda

// map, add, identity now all typed

I’m new to flow, so it’s unclear to me whether this is an issue with the declarations in this repository, a result of some misunderstanding on my part, or a shortcoming of flow itself.

cc @alexeygolev @jeffmo. Thanks for your contributions so far.

[alexeygolev]

Just a quick update. Still working on it. Should be able to submit a PR before Monday. Found a couple of wrong typings along the way:-P

[jeffmo]

Support for both named and default exports inside a declare module will ship in 0.28 (no later than early next week). In the meantime, declare module bodies can only export one or the other:

Named via declare module.exports: {namedExport1: number, namedExport2: string}; Default via declare module.exports: MyDefaultExportHere;

In 0.28 and beyond, it will be possible to do:

declare module "MyModule" {
  declare export var namedExport1: number;
  declare export var namedExport2: string;
  declare export default MyDefaultExportHere;
}