Major code refactor. Migrate to null-safety. #93
Merged
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.
Changelog:
NumberPicker.integer
is nowNumberPicker
.NumberPicker.decimal
is nowDecimalNumberPicker
.NumberPicker.horizontal
is nowNumberPicker
withaxis: Axis.horizontal
infiniteLoop
to make it possible to go to null safety. The feature will come back once theinfitniteListView
package gets null-safe.animateInt
method and replaced it with just reacting to value changed (see example).Curves.easeOutCubic
.initialValue
tovalue
to avoid confusion from my awful naming.highlightSelectedValue
as it can be obtained by providingselectedTextStyle
.Closes #89
Closes #43
Closes #26
Closes #94