missingKeyHandler is called even when translations exist if I use a custom backend.ajax

Hello,

I am experiencing an issue with the following configuration (using i18next-react and this backend plugin):

i18n
   .use(initReactI18next)
   .use(i18nextXHRBackend)
   .init({
      lng,
      fallbackLng: defaultLng,
      debug,
      ns: ['common'],
      defaultNS: 'common',
      interpolation: {
         escapeValue: false
      },
      saveMissing: true,
      missingKeyHandler,
      backend: {
         loadPath: loadPathBaseUrl + '/i18n/{{lng}}/{{ns}}.json',
         ajax: loadLngAJAX,
         crossDomain: true
      }
   });
export default i18n;

If I use a custom missingKeyHandler and a custom backend.ajax callback, missingKeyHandler gets fired even when translations exist and are loaded (I see messages in the console if debug is true and my missingKeyHandler is called).

If I comment this line out:

...
//ajax: loadLngAJAX,
...

Everything works and missingKeyHandler is not fired (as it should be even when using a custom ajax with this backend plugin).

Do you think this is a bug or is there a reason why I am experiencing this behaviour?

Thank you for your attention.

[jamuhl]

Yes - not sure what happens - but in the end the code is dead simple…ajax and missingHandler have nothing todo with each other only if the ajax call somehow does not provide the data in correct format for parse (which is a JSON.parse) to succeed. That is what fails currently and your parse dummy “fixes” - the underlying problem still is in your ajax implementation.

But like you say - works with both - so: If it’s ok for you - it’s ok for me 😁

[tonix-tuft]

Yes, but I needed to override it with a dummy hook which just return the value because as I understood parse is called by the callback with the translation data passed to it.

Otherwise I am experiencing the misleading behaviour above, at least it works now.