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.
A couple of generics that mean we don't need to use AnyView, which could improve performance since view type information is no longer erased.
By the way, I was poking at this more to figure out how it worked, and your solution is super clever. I was trying to do it the other way around: get the
UIInterpolatingMotionEffect
to write to a property in UIKit, then exfiltrate the value of that property up to SwiftUI. But yours works the other way around: it wraps a SwiftUI view in a UIView and then applies the motion effects to the wrapper. I dig it!