-
Notifications
You must be signed in to change notification settings - Fork 24k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for nested AnimatedValues in AnimatedStyle (like shadowOffset) #11030
Closed
tuckerconnelly
wants to merge
1
commit into
facebook:master
from
tuckerconnelly:add-support-for-nested-animated-styles
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1471,21 +1471,25 @@ class AnimatedStyle extends AnimatedWithChildren { | |
this._style = style; | ||
} | ||
|
||
__getValue(): Object { | ||
var style = {}; | ||
for (var key in this._style) { | ||
var value = this._style[key]; | ||
// Recursively get animated values for nested styles (like iOS's shadowOffset) | ||
__walkStyleAndGetValues(style) { | ||
return Object.keys(style).reduce((prev, curr) => { | ||
let value = style[curr]; | ||
if (value instanceof Animated) { | ||
if (!value.__isNative) { | ||
// We cannot use value of natively driven nodes this way as the value we have access from | ||
// JS may not be up to date. | ||
style[key] = value.__getValue(); | ||
value = value.__getValue(); | ||
} | ||
} else { | ||
style[key] = value; | ||
} else if (typeof value === 'object') { | ||
value = this.__walkStyleAndGetValues(value); | ||
} | ||
} | ||
return style; | ||
return { ...prev, [curr]: value }; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's avoid creating a new object at each iterations and just mutate the initial one. |
||
}, {}); | ||
} | ||
|
||
__getValue(): Object { | ||
return this.__walkStyleAndGetValues(this._style); | ||
} | ||
|
||
__getAnimatedValue(): Object { | ||
|
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will cause issues with Array and null, if I remember correctly both of those will have type object but we don't want to traverse those.