<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="return {
            …state,
            msg: action.value
            };"><pre class="notranslate"><code class="notranslate">return {
            …state,
            msg: action.value
            };
</code></pre></div>
<p dir="auto">my jsconfig.js:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="{
    &quot;compilerOptions&quot;: {
        &quot;target&quot;: “ES7”,
        &quot;module&quot;: “es6”,
        &quot;experimentalDecorators&quot;: true
    }
}"><pre class="notranslate"><code class="notranslate">{
    "compilerOptions": {
        "target": “ES7”,
        "module": “es6”,
        "experimentalDecorators": true
    }
}
</code></pre></div>
<p dir="auto">anything else i forget to set?</p>
<p dir="auto">… and I can't turn it off by setting <code class="notranslate">javascript.validate.enable</code> false.</p>
<p dir="auto">Perhaps this is a soft documentation bug: the <a href="https://code.visualstudio.com/Updates" rel="nofollow">release notes</a> proudly mention <code class="notranslate">experimentalObjectRestSpread</code> but then say:</p>
<blockquote>
<p dir="auto">Support for ObjectRestSpread is not yet provided by Salsa but it is on the roadmap (see <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="58475863" data-permission-text="Title is private" data-url="https://github.com/microsoft/TypeScript/issues/2103" data-hovercard-type="issue" data-hovercard-url="/microsoft/TypeScript/issues/2103/hovercard" href="https://github.com/microsoft/TypeScript/issues/2103">microsoft/TypeScript#2103</a>).</p>
</blockquote>
<p dir="auto">… which is confusing and misleading.</p>
<p dir="auto">It's confusing because the stand-out tone of core dev responses to that issue is "not until TC39 moves it to stage 3; bother them, not us", which is much less optimistic than the Feb 2016 release notes or the <a href="https://github.com/Microsoft/TypeScript/wiki/Roadmap">TypeScript Roadmap</a> itself.</p>
<p dir="auto">It's misleading because it fails to <strong>describe the impact</strong> of "support… not yet provided" as <strong>error messages you can't make go away</strong>. If there's some way to make them go away, please describe it in that part of the release notes. If not, I don't think it's too strong to outright <strong>advise users of object spread properties to delay upgrading</strong>.</p>
<p dir="auto">Without a work-around, this kills <code class="notranslate">code</code> for me, as I now have to dig for the real errors amongst a few dozen erroneous:</p>
<ul dir="auto">
<li><code class="notranslate">Property assignment expected.</code></li>
<li><code class="notranslate">Argument expression expected.</code></li>
<li><code class="notranslate">Declaration or statement expected.</code></li>
</ul>
<p dir="auto">I trust a workaround is possible, as <code class="notranslate">code</code> is not erroring in JSX.</p>