Allow GoogleApiWrapper() HOC to be initialized with data from props

[mruoss]

This pull requests enhances the GoogleApiWrapper HOC by the possibility to initialize it with data from props by accepting a function as argument when initializing the HOC. The function will be called by the HOC by passing it the props passed to the HOC.

This solution inspired by the recompose bundle (e.g. the HOC withProps()) and is completely backwards compatible.

With this change, the GoogleApiWrapper can be used the same way as before:

GoogleApiWrapper({
  apiKey: (YOUR_GOOGLE_API_KEY_GOES_HERE),
})(MapContainer)

Additionally it can be initialized with a function as described above:

GoogleApiWrapper((props) => ({
  apiKey: props.apiKey,
  language: props.language,
}))(MapContainer)

Or, as in our case, the HOC can be used with redux and recompose:

const mapStateToProps = (state) => ({
	lang: selectLang(state),
})

const enhance = compose(
	connect(mapStateToProps),
	GoogleApiWrapper(({ lang }) => ({
		apiKey: 'API_KEY',
		language: lang,
	})),
)

export default enhance(MapContainer)

[auser]

I <3 this feature! Can you add a bit to the README describing this?

[mruoss]

Absolutely. I added the simple example of the alternative configuration to the README. Also noticed I had based my branch on an old version of master. It should be free of conflicts now.

Edit: Oh well no wonder I was based on an old version - you pushed like 700 commits today ;)

[rangoo94]

Nice idea, but I think that it's worth to rebuild it on props change as well. What do you think?

[auser]

I agree. Wanna add a PR @rangoo94?

[rangoo94]

No problem, I will do it today.

[rangoo94]

I added PR with update: #178

[mruoss]

Thank you very much @rangoo94. My approach was indeed not complete.

[rangoo94]

No problem, you're welcome :)