Removed update operators from number unary operators #5940
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
jridgewell
approved these changes
Jul 11, 2017
existentialism
added
pkg: types
PR: Docs 📝
existentialism
approved these changes
Jul 12, 2017
hzoo
reviewed
Jul 12, 2017
| @@ -43,7 +43,7 @@ export const BINARY_OPERATORS = [ | |||
| ]; | |||
|
|
|||
| export const BOOLEAN_UNARY_OPERATORS = ["delete", "!"]; | |||
| export const NUMBER_UNARY_OPERATORS = ["+", "-", "++", "--", "~"]; | |||
There was a problem hiding this comment.
This is also a breaking change haha
There was a problem hiding this comment.
That's why we're in alphas. I'd be surprised if anyone actually used this, though.
lock
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.
I discovered that the docs of babel-types on the website have a small mistake:
UnaryExpressionallows update operators++and--. But these are already covered by theUpdateExpressionnode. I was told by @jridgewell to remove them here in order for correct documentation to be generated.