You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the new named slots synta.
I have a component which dispatches async request and then uses received value in render. With named slots it was okay to have this kind of structure, so that I don't need to check every time whether the data is there. Is there a workaround for new slots?
Before:
<my-component><templatev-if="some !== null"> // this allows to have many nested components that use async data which is null initially
<templateslot="header"> // and here I use slot from my-component
<span>{{ some.nested.values }}</span></template><template><span> {{ some.nested.anotherValue }} </span></template></template></my-component>
Now:
<my-component><template#headerv-if="some !== null"> // check is in computed but still not good
<span>{{ some.nested.values }}</span></template><templatev-if="some !== null"><span> {{ some.nested.anotherValue }} </span></template></my-component>
The text was updated successfully, but these errors were encountered:
Hello, your issue has been closed because it does not conform to our issue requirements. In order to ensure every issue provides the necessary information for us to investigate, we require the use of the Issue Helper when creating new issues. Thank you!
Regarding the new named slots synta.
I have a component which dispatches async request and then uses received value in render. With named slots it was okay to have this kind of structure, so that I don't need to check every time whether the data is there. Is there a workaround for new slots?
Before:
Now:
The text was updated successfully, but these errors were encountered: