-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Ability to not document components vs ability to ignore components #168
Comments
There’s no ignore option (#11) yet. What option do you mean? |
Right now it's possible to ignore them through the config.
|
Then two options:
Update: I was wrong about the first option: these components would be ignored. |
Please check the docs updates in the previous commit: I’ve added some examples. |
Regarding point 2. I am not able to import modules in the examples. Maybe it works through modules inside node_modules that are resolved by webpack but if I want to import a "local" module then, how? Here is an example: in our docs, I've created a FakeBrowser component. The way I've found to make it work is to
Like this: section config (last section)
This is just an example. There are various different cases where I need components to be available to use in examples without them being documented, like private "helper components". |
FYI: |
Hello,
I'd like to make a difference between component I want to ignore completely vs not documenting them. Some components are "helpers" or "private" components. I'd like to be able to use them in code examples without documenting them.
But, I still need styleguide to load them which is not possible with the current ignore option and so the application will throw an error.
Other use case and way to think about it: how can I make some components available in the whole documentation so that they can be used in code examples, without documenting them?
The text was updated successfully, but these errors were encountered: