Skip to content
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

Support re-initialize #2323

Merged
merged 5 commits into from
Jul 12, 2023
Merged

Conversation

drewhamilton
Copy link
Contributor

Closes #2245, see details there. This resets L.networkFetcher in L.setFetcher, and resets L.networkCache in L.setCacheProvider, ensuring that the public fetcher and cache provider are never out of sync with their respective internal implementations.

LottieInitializeTest verifies this by simulating two tests run with different TemporaryFolder instances. The new test fails if either of the two L properties are not reset.

@gpeal
Copy link
Collaborator

gpeal commented Jul 11, 2023

I'm looking into the CI failure. For now, you can ignore it

@github-actions
Copy link

Snapshot Tests
API 23: Report Diff
API 31: Report Diff

@gpeal gpeal merged commit e82519d into airbnb:master Jul 12, 2023
6 checks passed
@drewhamilton drewhamilton deleted the drew/support-re-initialize branch July 12, 2023 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Re-calling Lottie.initialize leads to inconsistent state
2 participants