Support MDX routes

[brandonpittman]

Since MDX files can be routes, they should be supported.

Closes #5

[brandonpittman]

None of the nested routes work with MDX files. The top-level ones work, but that's Remix's normal behavior. Guess Remix's MDX support is taking precedence.

[kiliman]

Sorry, I don't use Remix's built-in MDX support, so never tested that... I'll see what I can do.

[kiliman]

Your patch is working fine for me on nested routes. Update published as v0.3.1

[brandonpittman]

Glad it worked! I’ll add a PR for the migrate tool too.

[brandonpittman]

@kiliman

Think I figured out my problem. I wanted to have a /reading and then a bunch of /reading/{...other stuff} routes.

If I don't create a layout in reading, the sub-routes don't render. If I try to just have /reading/index.mdx, that becomes the layout and the sub-routes don't render. But I also can't just have reading.index/index.md. There must be a /reading/{_layout,_route,index} file to get anything to render.

[kiliman]

If you don't want the parent to be a layout, then you need to suffix it with _.

reading_.whatever.mdx
OR
reading_/whatever/index.mdx

[kiliman]

Because in flat-routes, . is now the path separator, any flat routes in the default convention must use the _ suffix.

So default convention reading.whatever.mdx must be reading_.whatever.mdx