-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Per-file wrapper components #319
Comments
You can wrap your document by exporting a default component like that: ---
name: Page
menu: Some Menu
route: /page
---
import Wrapper from './path/to/wrapper'
export default (props) => (
<Wrapper {...props} />
) |
That isn't what I want to do though because then if I use the playground it shows up as part of my example code. You just close the issue and answer like I don't know common JS imports. |
But this wrapper won't be shown as part of your playground @wldcordeiro, this wrapper will be wrapped in the
Just the last one will show the code on your playground! |
It'd be awesome if aside from the root wrapper I could create one at a file level. I have a mono-repo where I may have one file that I want to wrap in a
Provider
with one store and another where I wish to use another store and it'd be convenient to be able to make a project level wrapper that sets up anything I know all the packages need and then be able to point to a wrapper for that file by adding to the top-matter like this?The text was updated successfully, but these errors were encountered: