refactor: remove onChangedNullable
, update onChanged
for null val…
#177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ues, and set
allowDeselection
default to falseThis commit introduces breaking changes:
Removed the
onChangedNullable
method to simplify the API and avoid developer confusion. TheonChanged
method now supports returning or callback with a null value. Developers must implement null checks in their code to handle nullable results fromonChanged
.The
allowDeselection
property now defaults tofalse
. Ensure your code explicitly sets this totrue
if deselection is needed. However, when the variant is multiple, theallowDeselection
property defaults totrue
.Please update your code to accommodate these changes.