Add option to disable page creation for each language

[jenkin]

I know that "support multi-language url routes in a single page component" is the main feature of this plugin, but if content and paths are managed by an external system (ie. wordpress with wpgraphql and polylang) that feature becomes a problem. For example, if wpgraphql returns a page with original path /en/page-1, gatsby creates multiple pages with /en/en/page-1, /it/en/page-1, and so on.

I made a little change to make optional the creation of localized paths (localizedPaths option), without change the default behavior. In this case, language is extracted from original path with a custom function (languageFromPath option). You can see it here.

Of course, if you want, I can send you a PR.

[jimmyn]

Hi, thanks for the contribution, I will appreciate a PR, but I think your approach is all or nothing. Maybe we can add another option to specify a regex to enable this feature only for some paths.

Imagine the use case where you have a landing page that you want to automatically translate to all available languages, but you also have a blog section that fetches posts from some CRM. I think it would be handy to allow a user to specify

localizedPaths: /^\/([a-z]{2})\/blog/

[jenkin]

Good point, in the latest commit I changed localizedPaths from boolean to regexp and now onCreatePage test for regexp match of path.

[jenkin]

I notice there is also a problem with Link component, it ignores this new option and prepend language to all linked routes, breaking links... 🤔

[jimmyn]

@jenkin this should be solved in the latest release. Check new pages option.