This repository has been archived by the owner on May 19, 2018. It is now read-only.
Freeze current plugins list for "*" option, and remove from README.md #245
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
3 tasks
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.
Discussed this with @loganfsmyth and @hzoo a bit. While I love the convenience of having a
*option, it leads to conflicts when we have conflicting plugins. Right now, this has come up when trying to work on the new decorators proposal (which forbids syntax allowed in the old proposal). But, I can also see this coming up if we ever wanted, say, a TypeScript parser plugin, which would conflict with the Flow plugin.