Implement support for declare on class fields with Flow
#11176
Closed
Conversation
This file contains 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
nicolo-ribaudo
added
PR: New Feature 🚀
|
I closed this PR because new commits didn't appear, and...
Reponed at #11178 |
github-actions
bot
added
the
outdated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Flow has recently landed support for
declarefields, similar to TypeScript. (facebook/flow@11b7adb)This PR implements parser support, and adds an
allowDeclareFieldsoption to the transform plugin to mirror the one of@babel/plugin-transform-typescript. In Babel 8 it will be enabled by default.Even if it's not released yet in Flow, I'm adding this to the v7.9.0 milestone since Flow is released about once a week.
cc @mroch