fix: add language prefix for dynamic routes

[krotovic]

This PR should fix the #57 issue.

Gatsby uses page.matchPath for client-side routes and this plugin never changes that to add language prefix.

Reference: https://www.gatsbyjs.com/docs/gatsby-internals-terminology/#matchpath

[MarcoG3]

Quick workaround I'm using based on your contribution which is useful to avoid installing this PR as a dependency.

In gatsby-node.js

exports.onCreatePage = ({ page, actions }) => {
  const { createPage, deletePage } = actions;

  if (page.matchPath === '/your-path/:id') {
    deletePage(page);

    createPage({
      ...page,
      matchPath: page.context.language !== page.context.i18n.defaultLanguage ? `${page.context.language}/your-path/:id` : page.matchPath,
    });
  }
};

[krotovic]

@jimmyn Still no progress on this PR?

[jamesdamild]

hi @jimmyn , i am working with this gatsby project, when I create client routes with the createPage.
the English version works fine which is the default, but when i change to the french, the url changes to :http://localhost:8000/fr/fr/checkout/, it's adding double fr on the path. any help why it's doing that ?

here is my createPage on the gatsbynode:

if (page.path.startsWith(`/checkout`)) {
    page.matchPath = `/checkout/*`
    createPage(page)
  }

here is the router for it on the checkout page under the page folder:
<Router> <AuthenticatedRoute path='/checkout/:cartId' component={Home} /> <AuthenticatedRoute path='/checkout/:cartId/payment' component={Payment} /> <NotFound default /> </Router>

help please any idea why it does that ?

thanks