Adding addon-options makes input from addon-knobs sluggish and unpredictable

Describe the bug When adding the withOptions decorator, input from knobs became sluggish.

To Reproduce Steps to reproduce the behavior:

1. Add addon-options to existing project which uses addon-knobs already, according to instructions.
2. Setup withOptions with an empty object addDecorator(withOptions({})).
3. View a story with knobs and edit text.

Expected behavior Input behaviour should not feel sluggish, and the typed string should be correct.

Screenshots Entering the string “Spain, a country with lots of fun and beaches” with the withOptions decorator added. Result is a garbled string of nonsense.

The same string “Spain, a country with lots of fun and beaches” without the withOptions decorator.

Code snippets If applicable, add code samples to help explain your problem.

System:

• OS: Windows 8
• Device: Desktop computer
• Browser: Chrome 70.0.3538.77
• Framework: React
• Addons: knobs, a11y, notes, options
• Version: 4.0.4

Additional context Having 13-14 components in my current project, and lots more to be done, I added the addon-options decorator to group components with the hierarchyRootSeparator option, but adding this made everything really sluggish. Commenting out the withOptions decorator makes every component work as expected again.

[ndelangen]

In V5 the options addon is deprecated, as it’s now using the addParameters api.

This should resolve this issue completely.

[tmeasday]

Hi @CodeByAlex! Sorry I wrote the above on my phone and I see it has autocorrected “debounce” to “denounce”!! 😅

Don’t worry, no-one is offended 😄 . I just figured you had more context than me and might be able to suggest a solution, which it seems you can!

I think it would definitely make sense to look at this in the ui-overhaul (now release/5.0 branch) as I believe knobs has changed there and in fact @shilman is currently working to get it (knobs) operational again before we merge release/5.0 to next. I’m sure he would appreciate any assistance and it may be a good time to fix this issue if it is still occurring there.