MDX documentation ArgsTable: "Args table with interactive controls couldn't be auto-generated" #23959
Replies: 3 comments
-
|
maybe about to #24618 ? |
Beta Was this translation helpful? Give feedback.
-
|
Try installing this package |
Beta Was this translation helpful? Give feedback.
-
|
For me it was stupidly simple - the table wasn’t generated because there was nothing to document. The component behind the story exposed no public inputs and outputs and the referenced story’s I use Compodoc and confirmed it by looking at the component’s entry in Example: <!-- my-story.mdx -->
import { Meta, ArgTypes } from '@storybook/blocks';
import * as MyStories from '../stories/my-story';
<Meta of={MyStories} />
<ArgTypes />@Component({ ... })
export class MyStoryComponent implements OnInit, OnDestroy {
// no inputs, outputs and public class members besides the angular hooks
ngOnInit() { ... }
ngOnDestroy() { ... }
}// my.stories.ts
const meta: Meta<MyStory> = {
component: MyStoryComponent,
args: {}, // nothing to document
};
export default meta; |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Facing the same issue in almost every somehow unique component.

All possible args are enabled. Tried: with arg, with argTypes, with both of them, without any at all - still doesn't work. Tried to remove and add each after another argument - no results. Tried to define types both in mdx and in story.
Code:
Even the message confuses me -- Args table with interactive controls couldn't be auto-generated? But why for some components it works? What does it mean interactive controls? I thought all controls are interactive.
Would be glad to get an advice <3
Beta Was this translation helpful? Give feedback.
All reactions