react-native autodocs support

[patrickkempff]

Describe the bug
I have enabled autodocs in my react-native storybook project, but I don't see docs page (globally or on component level). I added all the required configuration and also added the tags: ['autodocs'], key. Is autodocs even supported on react-native or react-native-web version of storybook? I searched a lot in the official document, GitHub, google etc. but I could not find anything.

To Reproduce
N/A

Expected behavior
Autodocs like in the storybook documentation

Screenshots
N/A

Code snippets
N/A

[JaccoM]

Same issue

[dannyhw]

Could you please explain what you mean? This package @storybook/react-native doesn't support docs the same way as the web.

For docs support you can use https://github.com/storybookjs/addon-react-native-web

dynamically rendering mdx at runtime is a bit tricky in react native on device but I have examples of how you can do custom docs

[cuicui-QoQ]

May I ask if there are examples of generating component documentation for the @storybook/react-native library? Currently, I need to provide documentation to my colleagues while using @storybook/react-native.

[dannyhw]

A solution for this is actually planned for after v10 but theres not a built in way yet.

You can manually add notes with the notes addon or add a Special story that overrides the render function to show some docs information

[cuicui-QoQ]

When is the v10 version planned to be released?

[dannyhw]

Late October is the planned release but all depends on how things go with the rc from storybooks core libraries

The beta is out though

[fabioatcorreia]

Any news on this?
Would be great to have built-in support for documentation on @storybook/react-native.

[dannyhw]

Unfortunately no significant update on my end. I have had some discussions about it with the web guys though.

Mostly this needs some help from the web team to understand the apis. Thing is its a bit unclear at the moment how to approach it. Theres some changes going on in core that might change how docs work, so might be smart to wait for that.

Anyway I haven't had the time for it yet. Theres a few other important features that would take priority over this.

1. Csf next/factories
2. Globals working and backgrounds working using same web apis
3. Consolidating addons into core

These will be more fundamental for compatibility with web and then docs will be high up on the list after that.