Default language not working as expected

Summary of the issue

Default language not working as expected. Default language is set to Spanish (es), but the root page gets redirected to English (en)

Expected behavior

✅ When visiting the index page http://mysite.com/ it should load the page normally using the default language Spanish (es)

Current behavior

❗ When visiting the index page http://mysite.com/ it gets automatically redirected to http://mysite.com/en/

Setup details

The allowed languages for the site are:

• English (en)
• French (fr)
• Spanish (es)

Version used:

    "gatsby": "^3.10.1"
    "i18next": "^20.4.0"
    "react-i18next": "^11.11.4"
    "gatsby-plugin-react-i18next": "^1.1.1"

Gatsby configuration:

{
      resolve: `gatsby-source-filesystem`,
      options: {
        path: `${__dirname}/locales`,
        name: `locale`,
      },
    },
    {
      resolve: `gatsby-plugin-react-i18next`,
      options: {
        localeJsonSourceName: `locale`,
        defaultLanguage: "es",
        languages: ["es", "fr", "en"],
        siteUrl: `http://mysite.com/`,
        i18nextOptions: {
          interpolation: {
            escapeValue: false,
          },
          keySeparator: false,
          nsSeparator: false,
        },
      },
    },
    
...
...
}    

[whitedwarf2000]

Hi @AnderUstarroz , I have added generateDefaultLanguagePage: true and redirect: false to options and it work for me

[nextlevelshit]

Guys, sorry to say, but read the docs…

Setting a defaultLanguage means that you will render this language, when the user navigates to root /. Instead of navigating him/her to /${defaultLanguage} it will show the index page with your choice.

It is super tricky to be honest. I am also struggling with many side effects, but the developers have done stuff intentionally. And pushing such PR like @chenxizhang did is a huge provocation. At least you could have stuck to the code style convention. Instead of reading the documentation you’re pushing such heavily unreflected changes to all of us? C’mon, you can do a better job!

If you want to gain full control of your client routes, you will probably need to implement a gatsby-node.js file or add a router into your pages/index.js for instance. If you want to know more, I am available for help.