Expose onUserAction via ref in UiContainer#102
Merged
tvanlaerhoven merged 2 commits intoTHEOplayer:mainfrom Jan 26, 2026
Merged
Expose onUserAction via ref in UiContainer#102tvanlaerhoven merged 2 commits intoTHEOplayer:mainfrom
tvanlaerhoven merged 2 commits intoTHEOplayer:mainfrom
Conversation
🦋 Changeset detectedLatest commit: 225caef The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
tvanlaerhoven
force-pushed
the
expose-onUserAction-as-ref
branch
from
094fdca to
225caef
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.
Summary
Exposes
onUserAction()via arefinUiContainer, enabling parent components to programmatically trigger the UI fade-in animation.Use Case
Currently, triggering UI visibility requires
PlayerContext, forcing parent components to be nested withinUiContainer. This change allows external logic (such as keyboard shortcuts) to control the UI state without strict component nesting.