feat: add async API compat layer for experimental migration#183
Merged
feat: add async API compat layer for experimental migration#183
Conversation
mfazekas
force-pushed
the
feat/async-api-compat
branch
3 times, most recently
from
71be8c5 to
47a158b
Compare
…patibility Add async equivalents for all sync ViewModel/RiveFile methods (createInstanceByNameAsync, getValueAsync, viewModelByNameAsync, etc.) and mark legacy sync methods as @deprecated. Native implementations wrap sync calls in Promise.async on both iOS and Android.
mfazekas
force-pushed
the
feat/async-api-compat
branch
from
47a158b to
bd05f51
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds async equivalents for all sync methods and marks the sync versions as
@deprecated. This lets users migrate to the new async API while still on the legacy backend, before switching to experimental.No behavior changes — all new async methods are thin
Promise.async {}wrappers around existing sync calls.