Removed restriction on output props type so it does not have to take …

[srmelody]

…all container props

In the current type definition, you have to pass all input props that the container is taking to the component that the container is managing the interaction with the meteor collections. In this change, I'm allowing the container to selectively pass props. This allows existing component libraries (Material-UI, react-bootstrap) to plug in without needing to wrap the components.

I'm using this change locally in my typings directory.

[srmelody]

@fullflavedave can you take a look at this pull request?

[fullflavedave]

I’ll take a look and merge it in tomorrow. Dave On Jun 29, 2017, at 7:41 AM, Sean Melody <[email protected]> wrote: @fullflavedave <https://github.com/fullflavedave> can you take a look at this pull request? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAhM2ptCehofYKdzVo-A06g6ds2XOFuAks5sI7eTgaJpZM4OIRqA>.

[fullflavedave]

Is the extra closing parenthesis on the changed line a typo?
export function createContainer<InP, D, OutP)>(

I have to admit that I haven't use TypeScript with Meteor for a while, and I don't have the time today to make sure it won't break existing usage (e.g. a managed component relies on the implicit forwarding of the container inputs). I'll take your word for it, though, unless anyone else chimes in.