<h3 dir="auto">Version</h3>
<p dir="auto">2.6.10</p>
<h3 dir="auto">Reproduction link</h3>
<p dir="auto"><a href="https://codesandbox.io/s/vue-template-7x6nl" rel="nofollow">https://codesandbox.io/s/vue-template-7x6nl</a></p>
<h3 dir="auto">Steps to reproduce</h3>
<p dir="auto">Use <code class="notranslate">v-slot</code> directive with "is" attribute</p>
<h3 dir="auto">What is expected?</h3>
<p dir="auto">similar behavior with the old syntax of slots</p>
<h3 dir="auto">What is actually happening?</h3>
<p dir="auto">scoped slot not working with dynamic component</p>
<h3 dir="auto">What problem does this feature solve?</h3>
<p dir="auto">When using mapGetters from vuex it would be nice to be able to provide the store namespace from a prop.</p>
<p dir="auto">The use case for us is, that we have several store modules whose interfaces basically look the same. If we could provide the store namespace as a prop we could rely on that interface from a specific component without having to duplicate the mapGetters calls in all parent components that use the component.</p>
<h3 dir="auto">What does the proposed API look like?</h3>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="computed: {
    ...mapGetters(this.storeNamespace, {'item': 'myGetter' })
}"><pre class="notranslate"><code class="notranslate">computed: {
    ...mapGetters(this.storeNamespace, {'item': 'myGetter' })
}
</code></pre></div>
<p dir="auto">See the following Codepen for a full example:</p>
<p dir="auto"><a href="https://codepen.io/dmnk_bln/pen/yMvpLq/" rel="nofollow">https://codepen.io/dmnk_bln/pen/yMvpLq/</a></p>