We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
undefined
null
It is confusing now, some components need undefined when we want to clear value of a property, but others need null.
We should unify the behaviors of all the components, and they should:
This will be a breaking change, so we should do this in next major version.
cc @warmhug
The text was updated successfully, but these errors were encountered:
+1 for this
Sorry, something went wrong.
+1, undefined should mean "a unintentional empty value" so it could be a hint of a future error, leave null as the behavior of intentional clear value
This had been resolved in antd v4.
No branches or pull requests
It is confusing now, some components need
undefined
when we want to clear value of a property, but others neednull
.We should unify the behaviors of all the components, and they should:
undefined
as undefined, even if developers passundefined
to components explicitnull
as defined, and it means clear the value of a propertyThis will be a breaking change, so we should do this in next major version.
cc @warmhug
The text was updated successfully, but these errors were encountered: