Skip to content
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

Remove useDefaultValueIfUndefined optional feature, make it default behavior #1283

Merged
merged 1 commit into from
Oct 13, 2020

Conversation

simonihmig
Copy link
Contributor

As discussed in #1282 (comment), we remove the optional feature introduced in #1248 again, and make its behavior the default one.

@simonihmig
Copy link
Contributor Author

Only failing for Canary, which should be fixed by #1284

…ehavior

As discussed in #1282 (comment), we remove the optional feature introduced in #1248 again, and make its behavior the default one.
@jelhan
Copy link
Contributor

jelhan commented Oct 12, 2020

I think this should be mentioned in the changelog. Not that sure about the title so. Technically it's about removing the optional feature. But from a consumer point of view it's about supporting passing arguments through without needing to worry about default values. I guess for better changelog the title should focus on that one.

@simonihmig simonihmig changed the title Remove useDefaultValueIfUndefined optional feature, make it default behavior Apply default values even if undefined is passed, allowing for easy wrapping of components Oct 13, 2020
@simonihmig simonihmig merged commit 1716d77 into master Oct 13, 2020
@simonihmig simonihmig deleted the undefined-fallback branch October 13, 2020 08:51
@simonihmig
Copy link
Contributor Author

Changed the title. Feel free to change again if you have something better, at least until it's release time again! 😉

@simonihmig simonihmig changed the title Apply default values even if undefined is passed, allowing for easy wrapping of components Remove useDefaultValueIfUndefined optional feature, make it default behavior Oct 13, 2020
@simonihmig
Copy link
Contributor Author

Just reverted that, and added the title and label to your PR, so you are correctly credited for that change! 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants