Bug Fix: Bug when setting initialDate to December in ScrollWheelDatePicker #10
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.
Fixes #9
Problem
When setting
initialDate
to a date in December, theScrollWheelDatePicker
throws an error due to state changes being triggered during the widget's build phase. This issue occurs because theDateController
callsnotifyListeners
directly during initialization.Solution
WidgetsBinding.instance.addPostFrameCallback
to delaynotifyListeners
until after the current frame is built. This prevents the error caused by state changes during the build phase._dayController
initialization to properly handle the month value, ensuring December (month 12) is processed correctly.Impact
initialDate
is set to December.notifyListeners
is only called after the build phase is complete.Code Changes
Before (causing the error):
After fix