export internal API for user customisations

[pbadenski]

Resolves #20

• export createMappedSelectorCreator, memoizeMap & memoizeList
• add relevant TypeScript typings

[pbadenski]

@heyimalex Have you had a chance to look at it?

[heyimalex]

Does this create a hard dependency on immutable?

[pbadenski]

Oh yeah, I think it does - is that a problem?

[pbadenski]

@heyimalex hi, just a friendly reminder ;) would you like me to remove that "hard dependency"?

[heyimalex]

Sorry, I'll take a look tonight!

[Domiii]

Bump...? 😄

I guess, the library is already depending on immutable, for some reason...? (see here)

[heyimalex]

Sorry, I'll try and find some time soon!

RE: Immutable, right now it's a devDependency, so people who npm install don't need to have it installed. Using it in the types would make it an actual dependency. Maybe ts has a better way to handle this now (specifically methods that return this-type), or just some way to make it ergonomic, but I'll need a little time to think about it.

[heyimalex]

My thoughts on this right now are I can cut a release exposing the functions you need, but adding type definitions seems too difficult. If you want to try and get this running I think it'll take more than what's currently in the pr.

[heyimalex]

Released 1.0.6, lmk if that solves your problem

[pbadenski]

Thanks! I should get around to it soon and will let you know!

[Domiii]

@heyimalex Did you, by any chance, publish it to NPM but forgot to push it to the repo?

[heyimalex]

@Domiii Haha my bad, it should be up now

[Domiii]

I definitely prefer your solution over this PR, as it is clean and does not suddenly change the entire purpose of the library. Sweet!

[pbadenski]

@heyimalex I think ideally you might want to consider a separate library with ImmutableJS support (e.g. reselect-map-immutable). I don't think it's possible to add any type definitions for ImmutableJS part of the library otherwise without creating hard dependency on ImmutableJS.