<p dir="auto">Please port icons to next release. Or are you planning to move them into separate package? Cause now i can't move from <code class="notranslate">0.16.7</code> to <code class="notranslate">next</code></p>
<p dir="auto">Hi, I don't believe this is a duplicate, but I've found that spreading "extra" props into the <code class="notranslate">component</code> prop is confusing and counter-intuitive (info found here: <a href="https://stackoverflow.com/questions/37843495/material-ui-adding-link-component-from-react-router" rel="nofollow">https://stackoverflow.com/questions/37843495/material-ui-adding-link-component-from-react-router</a>). It would make a lot more sense to allow an actual <code class="notranslate">render</code> prop that can be used to actually render out a component.</p>
<p dir="auto">For example:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="// current implementation for a Tab with a Link

&lt;Tab
    value=&quot;tabOne&quot;
    component={Link}
    to={`/orgs/${props.params.orgId}/members`}  // this prop doesn't exist in the docs, but it works
/&gt;"><pre class="notranslate"><code class="notranslate">// current implementation for a Tab with a Link

&lt;Tab
    value="tabOne"
    component={Link}
    to={`/orgs/${props.params.orgId}/members`}  // this prop doesn't exist in the docs, but it works
/&gt;
</code></pre></div>
<p dir="auto">Result from proposed change:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&lt;Tab
    value=&quot;tabOne&quot;
    render={&lt;Link to=&quot;/my/relative/path&quot; /&gt;}
/&gt;"><pre class="notranslate"><code class="notranslate">&lt;Tab
    value="tabOne"
    render={&lt;Link to="/my/relative/path" /&gt;}
/&gt;
</code></pre></div>
<p dir="auto">This would make implementation a lot more intuitive.</p>