fix: remove view config mismatches #2642
Merged
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:
Static View configs are a mechanism that React Native uses to ensure that the props and events a native component has match between JS and native. The JS side is statically defined, while the native side is generated based off the view manager (paper only). I think in Fabric, JS is the source of truth completely.
While running RNTester in Fabric, there were a bunch of Redbox warnings warning of static view config mismatches. This might be because we are using views through the interop layer, or there is still validation running that checks against the paper view manager even if we aren't using it. While we have these warnings, let's fix them.
Test Plan:
Launch RNTester on both iOS and macOS from this repo and see no Redboxes warning of mismatches.