-
Notifications
You must be signed in to change notification settings - Fork 17
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
v5.2.5: Only first change of a knob is registered #30
Comments
@Hypnosphi could this be hooks-related? |
Maybe |
@Hypnosphi I think there might be a hooks patch that didn't make it into Would you mind patching it over? |
Not until Friday, sorry |
Weird, I only see conflicts in |
@shilman unfortunately, I can't test it on
|
I'm also having this issue, but when I downgrade @storybook/* from 5.2.5 to 5.1.9, I get an error saying that none of my stories can be found. Is there a difference in setup between version 5.2.x and 5.1.x? |
Same issue here. We cannot downgrade because we already migrated several stories to the new format :/ Is there anything we can do to help merging the fix? |
@Hypnosphi Here's what I did:
However, the test fails:
Help getting this merged would be much appreciated. |
I have 2 failing tests on clean master:
UPD: it's storybookjs/storybook#6490 |
@shilman |
@Hypnosphi yes please! |
OK I did, but wasn't able to test it manually because "Hooks" kind gives me a blank page with following exception:
An express debugging showed that Looks like something went wrong with telejson deserialization cc @ndelangen |
It's unclear to me if you guys have a handle on this or not but with For example this will cause the knob to stop applying changes AFTER the .add('Default', () => {
const [name, setName] = useState('')
const width = number(
'Width',
42,
{
min: 1,
max: 100,
step: 1,
range: true,
},
)
return (
<div
style={{ width }}
onClick={() => setName('foo')}
>
{ foo }
</div>
}) |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Hi gang, We’ve just released addon-controls in 6.0-beta! Controls are portable, auto-generated knobs that are intended to replace addon-knobs long term. Please upgrade and try them out today. Thanks for your help and support getting this stable for release! |
For anybody who is interested in Controls but don't know where to start, I've created a quick & dirty step-by-step walkthrough to go from a fresh CRA project to a working demo. Check it out: => Storybook Controls w/ CRA & TypeScript There are also some "knobs to controls" migration docs in the Controls README: |
Describe the bug
Only the first change to a text or number field (probably other types as well) registers and causes the component to update. It seems to be caused by there being a single
set
event (for which there is a listener) and no listeners for the subsequentchange
events.To Reproduce
Steps to reproduce the behavior:
storybookjs/knobs/set
storybookjs/knobs/change
for each subsequent changeExpected behavior
The console should rerender
Screenshots
This screenshot shows there are 0 listeners registered for the change event:
Code snippets
System:
npx -p @storybook/cli@next sb info
just hangs and never gets past this output:My manual way:
Additional context
Reverting
@storybook/*
to v5.1.9 will fix the issue.The text was updated successfully, but these errors were encountered: