Fix bad types for new Translate component

Some bad flow type definitions were committed in v2.17.0 - this should fix those issues.

Add Translate component

• Add new <Translate /> component which is now the recommended way to access translations in your components.
• Deprecate localize HOC method
• update docs

Updates to translate and localize

• translate function now accepts defaultLanguage option. See How do I retrieve a translation for a language other than active language? for details.
• localizeHOC now accepts new param getStateSlice. See Can I use ImmutableJS? for details.

Minor fixes

• Update localize to handle state objects which are maps #49
• Update broken links in docs

Small fix to type defintions

update type definitions to make missingTranslationMsg optional

Add new option for custom missing translation messages

You can find updated docs on how to use new feature here:

• Custom missing translation messages
• missingTranslationMsg

Fix bad import on flow definition

v2.13.8

2.13.8

Guess what .... TypeScript fix!

Fixes issue #35 (incorrect type definition for localize method)

Yet another damn type definition fix 😇

• Overhauled the flow type structure, as it was not properly exporting declared functions
• Fixed a couple of the type defs that were incorrect

Type defintion fixes

• move flow types into the index file as they were not being exported properly
• fix Translate type for both typescript and flow, as data param was incorrectly labeled as required