fix(module: select): can not set initial value for non-datasource approach #1743
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.
🤔 This is a ...
🔗 Related issue link
Fixes #1735
💡 Background and solution
A sample:
This issue is introduced by #1720 . In #1720, I changed the position to call
OnValueChange
method. In most cases, this change is safe. However,OnValueChange
should do nothing for the first call(by evaluating the_isInitialized
field), but the method is now first called after_isInitialized
is set totrue
. We can solve this issue by simply move_isInitialized = true;
to after the call toOnValueChange
. Let me know if you think we should use a new variable or variable name in this case.📝 Changelog
☑️ Self Check before Merge