feat(rive): stateChange event for state machine transitions #18
+23
−6
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.
Title
Add
stateChange
event for RiveView (iOS + Android)Summary
Exposes State Machine transitions from the native Rive runtimes to JS.
Works the same on both platforms.
Changes
common.ts
– adds missingstateChangedEvent
constant.RiveStateMachineDelegateImpl
– callsowner.notify({ eventName: 'stateChange', ... })
.index.d.ts
– declareson('stateChange', ...)
for type safety.Why
Apps need to react when a Rive State Machine enters a new state (e.g. to chain logic or UI).
Until now this info was only available inside native code.
No breaking changes; existing code keeps working.