[Bug]: Boolean control is not persistent

[Spielboerg]

Describe the bug

As the title suggests, boolean controls are not persistent when the page is reloaded. On the one hand, it logs unnecessarily many warnings and on the other hand, direct links to stories with control values in it cannot be sent to someone else.

See the Reproduction section for more information.

To Reproduce

https://stackblitz.com/edit/github-fbee7n?file=src%2Fstories%2FButton.stories.js

Preparation: Do not use the inline preview but open the preview in a new tab (button on the upper right). Only in this way it is possible for you to see the changes in the URL.

Successful case:

1. Go to the Button/Primary story
2. Clear the logs in the browser dev tools
3. Click on the primary control to change it to false.
   • Notice that &args=primary:!false is added to the URL
   • Notice this warning in the logs:

     Omitted potentially unsafe URL args.
     
     More info: https://storybook.js.org/docs/react/writing-stories/args#setting-args-through-the-url
     

4. Reload the page
   • Notice the &args=primary:!false is still in the URL and the primary control is set to false
   • Notice that the warning from 3. above is logged again.

Failing case:

1. Go to the Button/Secondary story
2. Clear the logs in the browser dev tools
3. Click on the primary control to change it to true.
   • Notice that &args=primary:!true is added to the URL
   • Notice this warning in the logs:

     Omitted potentially unsafe URL args.
     
     More info: https://storybook.js.org/docs/react/writing-stories/args#setting-args-through-the-url
     

4. Reload the page
   • Notice the &args=primary:!true is no longer in the URL and the primary control is set to false
   • Notice that the warning from 3. above is logged again.

System

No response

Additional context

No response

[shilman]

Jiminy cricket!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.28 containing PR #22807 that references this issue. Upgrade today to the @next NPM tag to try it out!

npx sb@next upgrade --prerelease

[demeshkin]

@shilman I don't think the issue is fixed. When passing !true arguments in URL &args=primary:!true it's changes to false in the control.

[NiklasPor]

We're using buildArgsParam inside some tests which run against our Storybook and it includes the same issue. For now we're required to do some search & replace to remove the ! before true and false which keep storybook from interpreting them correctly.

[MichaelAllenWarner]

Yes, I see this behavior in my projects as well. The exclamation mark is getting wrongly added to boolean args set from the Controls.

[RJesusTVD]

Hello,

Any updates on this bug?

Thanks

[Nicolas-Menettrier]

Same behavior on my project too, I used @NiklasPor suggestion as a quick fix. Does the job

[shilman]

closing as duplicate to #25035