Mock REAInitializer for backward compatibility#4880
Merged
Conversation
piaskowyk
deleted the
@piaskowyk/add-fallback-for-backward-compatibility
branch
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
May 11, 2024
## Summary In #4619 @piaskowyk removed `REAInitializer` because it was no longer required. To avoid a breaking change, in #4880 he restored `REAInitializer` with no-op implementation for backward compatibility. This PR removes `REAInitializer` which effectively does nothing since 3.5.0. ## Test plan Build Example app on iOS.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Fixes #4631
In #4619 I removed REAInitializer because it is no longer needed. However, some brownfield apps still use it. This PR adds a mock for REAInitializer to ensure backward compatibility.
Test plan
CI