Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Summary: Ahead of enabling the `exact_empty_objects` option, suppress errors so that actually enabling the option is easier. We can do this without enabling the option by codemoding `{}` to `{...null}` in files that have errors. Process: 1) Get list of files with errors when enabling the option 2) Codemod `{}` to `{...null}` in those files 3) Suppress resulting errors 4) Land diff with `drop-conflicts` flag 5) Announce and enable option (with many fewer files to edit) 6) Codemod all `{...null}` to `{}` drop-conflicts We are working on making the empty object literal `{}` have the type `{}` - i.e. exact empty object - rather than being unsealed. More info in these posts: https://fb.workplace.com/groups/flowlang/posts/903386663600331, https://fb.workplace.com/groups/floweng/posts/8626146484100557 Reviewed By: pieterv Differential Revision: D37731004 fbshipit-source-id: a9305859ba4e8adbdb8ae8feff3ec8a2f07ed236
- Loading branch information