New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: replace _meta.json
in favor of _meta.{js,jsx,ts,tsx}
#852
Comments
💡 Also, we need to find a way to ignore accessing |
I like the idea! Allowing Like you said, the Next.js routing is also a problem. I think we can explore a solution here and if it's doable, 100% agree that we should add it! |
You are right, I guess I didn't find a way to ignore
I think for now we can skip support TypeScript and use JSDoc comment for validations types, it's better than nothing The main blocking problem for now, is to figure out how to import And also we make nextra/packages/nextra/src/loader.ts Lines 185 to 196 in 09b4102
nextra/packages/nextra/src/loader.ts Line 213 in 09b4102
|
I started to think again about this because I want to land this feature for remote MDX + versioning. I think I got an idea implementation, but it relies on I guess we can just make _meta.js a Next.js page (so we got .js, .jsx and .tsx support), and inject rewrites to force /_meta routes being /404. |
Closed #1168 |
First of all why?
main
blockmain
blockhttps://github.com/dotansimha/graphql-yoga/blob/1b018c3d2d347d3ca02eb0ca0175025325db6886/website/theme.config.tsx#L51-L64
to have possibility to sort sidebar items with the default eslint rule
sort-keys
and with eslint comment/* eslint sort-keys: error */
and omit installation of some JSON plugin to do ithave type safe
_meta
file since we can importMeta
type and have autocompleteExample: current
_meta
file with included some top and bottom content will looks likebefore
nextra/examples/swr-site/pages/docs/advanced/_meta.en-US.json
Lines 1 to 13 in 1a029e6
after
@shuding any thoughts? :)
The text was updated successfully, but these errors were encountered: