Should we rename Color and Animation to LottieColor and LottieAnimation in Lottie 4.0, to resolve naming conflicts with SwiftUI types?

[calda]

#1420 pointed out that the Lottie.Color and Lottie.Animation types create naming conflicts with SwiftUI's SwiftUI.Color and SwiftUI.Animation types. We could rename these to LottieColor and LottieAnimation, but this would be a breaking public API change.

We're planning on releasing Lottie 4.0 soon, which gives us the opportunity to make these sorts of breaking changes. In Lottie 4.0, should we rename Color and Animation to LottieColor and LottieAnimation?

[liudhzhyym]

Any new progress on this issue?
I have face same problem when I use lottie-ios in SwiftUI project

[calda]

I'm considering making this change in Lottie 4.0, but it would be a pretty sizable breaking change so I haven't decided yet.

[calda]

We've decided to rename these types in Lottie 4.0, which we are releasing later this month.

We'll introduce new names and deprecate the old names in Lottie 3.5 (consumers will get deprecation warnings with fix-its), and then remove the old names in Lottie 4.0 (there will no longer be any fix-its, since the old names won't exist anymore).

[calda]

#1761 renames these types, with deprecated typealiases for the old names. In Lottie 4.0 we will remove the typealiases, which resolves the SwiftUI naming conflict.