Expose applyProps - #634
Merged
Merged
Conversation
trezy
self-requested a review
November 17, 2025 17:37
trezy
self-requested a review
November 17, 2025 17:39
trezy
requested changes
Nov 17, 2025
trezy
left a comment
Collaborator
There was a problem hiding this comment.
Before we merge, @lunarraid, can you update the index test to verify this export isn't accidentally removed in the future?
https://github.com/pixijs/pixi-react/blob/main/test/unit/index.test.ts
|
🎉 This PR is included in version 8.0.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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.
In order to add a react-spring target, we need a way to 'natively' apply props without a re-render. I figure exposing this method is the easiest way to do so since it is what is called on render anyway.