Back out "RN: Adopt Mapped Types in EventEmitter" #38599
Closed
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:
Currently,
metro-config
does not havehermes-parser
enabled by default. This is becausehermes-parser
does not yet support parsing all of TypeScript's syntax nodes.However, this also means we cannot yet utilize any Flow langauge features that require the use of
hermes-parser
(and are unsupported by Babel). Mapped types falls into this category, so we cannot use them.This backs out a recent change that tried to adopt Flow mapped types in
EventEmitter
, for now. We can revisit after making the necessary changes tometro-config
.Changelog:
[Internal]
Reviewed By: pieterv
Differential Revision: D47729818