-
### Describe the bug
Autogeneration of Storybook Controls works properly for the following component declaration:
```tsx
function Component(props: {...}) {...}
export default Component
```
…
-
**Describe the bug**
I'm importing 'shared props' into multiple components using spread operator (see example + repro below), the component specific props show under the 'Props' heading within Storyb…
-
### Prerequisites
- [X] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [X] The issue still exists against the latest stable version of Elementor.…
-
these cyan lines are very thin and hard to see on some screens
see https://threejs.org/exam…
kfarr updated
4 months ago
-
Hi,
thank you for your addon !
I probably miss something, but I actually can't make the addon work. No error are displayed but my dependencies table is always empty.
--------------
package.j…
-
**Describe the bug**
At runtime, inside of a story, we need access to a (subset of) process.env to pass some values from the buildserver onto Storybook, and ultimately the application proper.
In S…
thany updated
2 months ago
-
**Describe the bug**
According to the docs, setting `control: false` in the `argTypes` should hide a control from the Controls addon, but keep it in the Docs page. However, I can't get this value to …
-
### Describe the bug
When export the react component with memo like this
`export default React.memo(Circle);`
Then in the doc "show code" part, it shows as this:
In storybook 7, it shows…
-
# 이슈
Wrapper, Default, Text에 등록된 Knobs가 세 곳에서 각각 독립적으로 관리가 되어야 하는데, 모든 Knobs들이 합쳐져서 세 …
-
### Describe the bug
### Summary
Hello, I am currently using Next.js14 version.
I applied the localFont application method as written in the official document, but the error as shown in the pic…