-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Addon-controls: Support undefined option for optional values #13259
Comments
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! |
@lifeiscontent see #14579. The TLDR is:
This was a decision discussed at length with @shilman and @domyen, it seemed a good compromise between over-complicating things and letting a user do what they want to do. |
Describe the bug
should have an option to set an arg to undefined if its optional
To Reproduce
Steps to reproduce the behavior:
2.Add an optional prop
Expected behavior
I'd expect that if an arg is optional, it should have
undefined
as a value in args.Screenshots
Code snippets
If applicable, add code samples to help explain your problem.
System
Please paste the results of
npx sb@next info
here.Additional context
Related bug that was fixed previously: #4487
The text was updated successfully, but these errors were encountered: