mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
pre-suppress errors before enabling experimental.object_freeze_fix (#47141)
Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/47141 D64152004 fixed a soundness hole in Flow's checking of frozen object types (e.g. try-Flow https://fburl.com/rmct2mf6). This diff suppresses Flow errors that appear when this fix is enabled (`experimental.object_freeze_fix` flag is set). For most of these cases the result of `Object.freeze()` is assigned to some variable typed as a mutable type. The variable is then passed to a context where its fields can be written to. Thus changing the annotation type to a readonly version would only cause more errors downstream. So, instead, these assignments are suppressed so that the choice of using Object.freeze can be revisited. Changelog: [internal] Reviewed By: SamChou19815 Differential Revision: D64699992 fbshipit-source-id: 48e4376d4ed3dbda21d32cabe512e6457384994f
This commit is contained in:
committed by
Facebook GitHub Bot
parent
d25f0c5edd
commit
363818ea20
@@ -18,5 +18,7 @@ if (__DEV__) {
|
||||
}
|
||||
export default ScrollViewContext;
|
||||
|
||||
// $FlowFixMe[incompatible-type] frozen objects are readonly
|
||||
export const HORIZONTAL: Value = Object.freeze({horizontal: true});
|
||||
// $FlowFixMe[incompatible-type] frozen objects are readonly
|
||||
export const VERTICAL: Value = Object.freeze({horizontal: false});
|
||||
|
||||
Reference in New Issue
Block a user