Disallow object destructuring via ESLint since we support Node v4 #2776
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.
In #2763 @dylanOshima got a cryptic CI error that only manifested in Node 4. It took a bunch of time to get the environment setup correctly to trigger that error correctly. It seems like the kind of thing that could be caught earlier with a lint rule, so I thought I'd add one.
Test plan:
Check out an early commit of #2763 and see this error: