Translations get cut off after 1 character.

Using the following I get a strange quirk…

interface HomePageState {
    translate: any;
}

type HomePageProps = HomePageState

class Home extends React.Component<HomePageProps, HomePageState> {   
    /// the below will only render "I"
    public render(): any {
        return <label>{ this.props.translate("home.slogan") }</label>;
   }
}

const addTranslateToProps = state => {
    console.log('state.locale', state.locale);
    // this will log out "translations: { home.slogan: "I'm the correct translation" }
    return {
        translate: getTranslate(state.locale)
    }
};

export default connect(
    addTranslateToProps
)(Home) as typeof Home;

To be clear: The translations state seems to contain the correct translation / localization, but the translate function exposed via props, does not work as expected.

I do believe it might be a dependent lib (reselect??) thats causing the problem, but not too sure… if anyone has encountered this before, any advice would be appreciated. I’m happy to supply any other information thats needed.

Other info: Stack is on top of dotnetcore, React + Redux + SSR (with webpack for bundling front end stuff)

[ryandrewjohnson]

@rohan-buchner would you be able to provide the following:

• a sample of your original translation data that you pass to addTranslate
• a look at how you are calling the initialize action? What are the languages And options you are passing? ( one strange thing I noticed is that your default language seems to be set to “localizations” which would mean you have a language code in your translation data with this name)
• what version of library are you using?

Also have you tried adding additional translations? Does this occur for others as well? If not I would try removing the apostrophe from “I’m” and see if that makes a difference. By any chance are you copy and pasting the content from another program like Word? If it is the apostrophe causing issues I suspect it could be an encoding issue.

Thanks

[ryandrewjohnson]

Glad it worked out. I think I’m going to try and tighten up the typings for the translation data, as that might help catch this issue for anyone using TypeScript or Flow.