Skip to content

fix: setting up default values, initial events emitting - #252

Merged
exploIF merged 5 commits into
mainfrom
@exploif/fix-default-values
Nov 17, 2025
Merged

exploIF merged 5 commits into
mainfrom
@exploif/fix-default-values

Conversation

@exploIF

@exploIF exploIF commented Nov 14, 2025

Copy link
Copy Markdown
Collaborator

exploIF and others added 3 commits November 14, 2025 14:52
Fixes:
#237
Turns out `eventEmitter` isn't available from the very beginning, but
the iOS code was remembering recently active styles even if no state
change event was emitted. This way, when the event emitter was finally
available, no state change event was emitted because recently active
styles were exactly same (even though no event went out).
Except that, I added all lifecycle callbacks
(`anyTextMayHaveBeenModified` that e.g. runs the state change event) to
the `didMoveToWindow` because it seems like the event emitter is defined
then.
The issue was;`defaultValue` was set but its state changes emitted only
when some change was done to an input (and not on focus or when
eventEmitter is available). The PR fixes both scenarios.

---------

Co-authored-by: Igor Furgała <74370735+exploIF@users.noreply.github.com>
@exploIF
exploIF merged commit 2788beb into main Nov 17, 2025
5 checks passed
@exploIF
exploIF deleted the @exploif/fix-default-values branch November 17, 2025 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Android list items aren't styled on first render BUG: Style changes emits if the user is not focused on the text field.

2 participants