tree d2a5d7baf51a8fc5b770e0cde0594ef3a99f3799
parent e2aaf91b150ad05e65f52fb72071622e545c368b
author Gabriel Peal <gpeal@users.noreply.github.com> 1626566344 -0700
committer GitHub <noreply@github.com> 1626566344 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg827ICRBK7hj4Ov3rIwAAi+kIAJkY4WICtI63NNLKbENV2hGz
 FazxboxAiRdUAf/svHz02dc6uMfilFHm/RWdEoq5Le1jeanTTE97aaoIRtw4/1dk
 Uk20G6GYSCR7WQkSngoeXYTOfoSs5E/BhxHnUahKamVRYd8PkEwGzJ/rSz8bXrYZ
 /WYuussjXIJ98vTGZ8r4uGiWu6kq9dplNQd7jBl1SX2BHLV2OvbuOQ4ywzr7Qkh0
 /sabrItjc9sCXruVzjuS6DA3D7+PeVbqydHOCVg9DBfSXCOr+Pjogaa5J3Th0zP0
 Bgf1vcY9jjZc06aORUXog4JsAsEZpQD/W99J4b7RGyR+qeOnGhK6bVck2DY0xNg=
 =DlZS
 -----END PGP SIGNATURE-----
 

[Compose] Allow custom cache keys, dynamic properties for images, and remove font remapping (#1847)

This set of changes is all around composition caching:

1) Increase the caching flexibility by allowing arbitrary cache keys.
2) Remove the cacheKey parameter from LottieCompositionSpec.JsonString because it was ambiguous with the new cacheKey parameter.
3) Add dynamic properties for bitmaps. This is helpful because it allows you to set a bitmap on a single LottieAnimation without overwriting the bitmap for the cacheable LottieComposition.
4) Removed fontRemapping for rememberLottieComposition because there was no way to know how to handle caching. Instead, dynamic properties can be used.