Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we suppress rest/spread "syntax" non-errors, for babel/ES6 .js? #7617

Closed
igrayson opened this issue Mar 21, 2016 · 1 comment
Closed
Labels
Duplicate An existing issue was already created

Comments

@igrayson
Copy link

This is not a feature request (for rest/spread operator) or a bug report (that rest/spread doesn't work).

  1. Is there a way to configure vscode today to suppress or otherwise not show as syntax errors the usage of the object spread operator?
  2. If this is not possible, should we update the public documentation about ES6 support (which today links to a summary of ES6 features including rest/spread) to indicate this lack of support?
@mhegazy
Copy link
Contributor

mhegazy commented Mar 21, 2016

ES6/ES2015 does not have support for rest/spread for object literals. nor will the next version ES7/ES2016. object rest and spread is a proposal for TC39 for ES8/ES2017. it is currently at stage 2, see https://github.com/tc39/ecma262#current-proposals. ES6 array spread is fully supported, and the documentation is accurate.

Suppressing the error is not sufficient. the whole system needs to know what it mean, so that formatting, editing, completion, etc.. work.

this is a duplicate of #2103, it is something on our road map and should be able to get to it shortly.

@mhegazy mhegazy closed this as completed Mar 21, 2016
@mhegazy mhegazy added the Duplicate An existing issue was already created label Mar 21, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

2 participants