feat: add support for implicit exact Flow types #471
Merged
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
Brianzchen
reviewed
Mar 15, 2021
This commit adds a support for implicit exact Flow types. This is especially useful when using `exact_by_default=true` Flow option and migrating towards `{ }` and `{ ... }` syntax (Flow standard is now to use `{ }` for strict objects and `{ key: value, ... }` for open objects).
Closes: #467
|
@gajus bump |
|
Hi, is there anything I can improve in this PR to make it mergeable? I would also like to offer my help with the maintenance of this project if needed. We are using this plugin for years and it's always been a pleasure. I would not like to see it slowly die. 😎 |
|
I cannot recall the reason I did not merge this the first few times it was bumped. Sorry about that. |
|
🎉 This PR is included in version 5.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit adds a support for implicit exact Flow types. This is especially useful when using
exact_by_default=trueFlow option and migrating towards{ }and{ ... }syntax (Flow standard is now to use{ }for strict objects and{ key: value, ... }for open objects).Closes: #467
TODO: