add support for remote [...catchAll] routes

[dimaMachina]

how look like catch all routes for graphql-eslint repository fetched from git

• add support for remote [...catchAll] routes
• sanitize remote mdx by removing import statements
• test collectCatchAll that adds to pageMap meta files and mdx pages
• fix hydration error
  for some reason remote mdx wrapped with <p/>

was caused by extra semi

• be capable provide missing components .<RemoteContent /> now accept components props
• be capable provide codeHighlight: true and defaultShowCopyCode: true while compiling remote mdx
• be capable auto-generate meta links for sidebar from dynamic _meta file with createCatchAllMeta()
• be capable of simple reordering above 👆
• be capable override internal URLs e.g. [hello](/docs/foo) => [hello](/docs/v2/foo) in remote mdx content
• folder renaming works for both folders with/without index page
• better folder structure

{
  "$YOUR_FOLDER_NAME": {
    "type": "folder",
    "title":  "$YOUR_NEW_FOLDER_TITLE",
    "items": {
      "$NESTED_PAGE": "$NESTED_PAGE_TITLE"
    }
  }
}

• support meta keys with / ❗️this no longer needed

[changeset-bot]

🦋 Changeset detected

Latest commit: fff9f6b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
nextra	Patch
nextra-theme-docs	Patch
nextra-theme-blog	Patch
example-blog	Patch
example-docs	Patch
swr-site	Patch
docs	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
nextra-theme-docs-dev	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 22, 2023 at 0:29AM (UTC)
nextra-v2	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 22, 2023 at 0:29AM (UTC)

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
nextra	⬜️ Ignored (Inspect)			Jan 22, 2023 at 0:29AM (UTC)

[shuding]

Amazing work! Left one thing for discussion

[shuding]

Have you considered the items proposal from #1239? Or supporting / in keys like:

{
  "configs": "configs",
  "getting-started": "getting-started",
  "getting-started/parser-options": "parser-options",
  "getting-started/parser": "parser"
}

[dimaMachina]

I think we can support both?

Update:

I guess the proposal with items is much nicer and later can be used for a global meta file

[dimaMachina]

@shuding after I realised that items solution couldn't be done because there is a case of existing mdx file and folder of the same name

{
  "foo": "Foo", // this is foo.mdx
  "foo": { // this is foo folder but this will overwrite foo file key
    "title": "Foo",
    "type": "Category",
    "items": {}
  } 
}

[shuding]

I think they need to be merged right? It's still 1 item on the sidebar 🤔

[dimaMachina]

they should not be merged so nextra under the hood will know if folder has folder index page or not

[shuding]

The tricky thing was i18n. If users can choose foo.en.mdx or foo/index.en.mdx (they point to the same URL), and when accessing /foo, the middleware doesn't know if it's foo.en or foo/index.en. So in the past I documented it as you'll always have to avoid index.en.mdx.

But I think overall the middleware based i18n solution is too hacky and I'd like to fix it properly. I have an idea for that and I'll probably start working on it soon!

[dimaMachina]

@shuding I still think that nested keys with slashes (I changed the order, now folders should end with slashes, like in .gitignore) are the most friendly way since less code is written.

With the above helper function, I was able to change the original order of items with a few lines coded

from

to

[shuding]

Wow amazing result!! Code LGTM!