grande slot
casino online con bonus
This page assumes you've already read the Components Basics. Read that first if you are
new to components.
Slot Content and馃搱 Outlet 鈥?/p>
We have learned that components can accept
props, which can be JavaScript values of any type. But how about馃搱 template content? In
some cases, we may want to pass a template fragment to a child component, and let the
馃搱 child component render the fragment within its own template.
For example, we may have a
template < FancyButton > Click
me!
The template of
this:
template <馃搱 button class = "fancy-btn" > < slot >
button >
The
slot content should be rendered.
And the final rendered DOM:
html < button class馃搱 =
"fancy-btn" >Click me!
With slots, the
rendering the outer
provided by the parent component.
Another way to understand slots is by comparing them
to JavaScript馃搱 functions:
js // parent component passing slot content FancyButton (
'Click me!' ) // FancyButton renders slot content in its own馃搱 template function
FancyButton ( slotContent ) { return `
` }
Slot content is not just limited to馃搱 text. It can be any valid template
content. For example, we can pass in multiple elements, or even other
components:
template馃搱 < FancyButton > < span style = "color:red" >Click me! <
AwesomeIcon name = "plus" />
By using slots, our
flexible and reusable. We can now use it in different places with different馃搱 inner
content, but all with the same fancy styling.
Vue components' slot mechanism is
inspired by the native Web Component
that we will see later.
Render Scope 鈥?/p>
Slot content has access to the data scope of馃搱 the
parent component, because it is defined in the parent. For example:
template < span >{{
message }} <馃搱 FancyButton >{{ message }}
Here both {{ message
}} interpolations will render the same content.
Slot content does not have馃搱 access to
the child component's data. Expressions in Vue templates can only access the scope it
is defined in, consistent馃搱 with JavaScript's lexical scoping. In other
words:
Expressions in the parent template only have access to the parent scope;
expressions in馃搱 the child template only have access to the child scope.
Fallback Content
鈥?/p>
There are cases when it's useful to specify fallback馃搱 (i.e. default) content for a
slot, to be rendered only when no content is provided. For example, in a
馃搱 component:
template < button type = "submit" > < slot >
We might
want the text "Submit"馃搱 to be rendered inside the
any slot content. To make "Submit" the fallback content,馃搱 we can place it in between the
template < button type = "submit" > < slot > Submit
Now when we use
providing no content馃搱 for the slot:
template < SubmitButton />
This will render the
fallback content, "Submit":
html < button type = "submit" >Submit
But馃搱 if we
provide content:
template < SubmitButton >Save
Then the provided
content will be rendered instead:
html < button type =馃搱 "submit" >Save
Named
Slots 鈥?/p>
There are times when it's useful to have multiple slot outlets in a single
component.馃搱 For example, in a
template:
template < div class = "container" > < header > < main > < footer >
For these cases,馃搱 the
element has a special attribute, name , which can be used to assign a unique ID to
different馃搱 slots so you can determine where content should be rendered:
template < div
class = "container" > < header > <馃搱 slot name = "header" > < main >
< slot > < footer > < slot name = "footer" >
div >
A
In a parent
component using
each targeting a different slot outlet. This is where named slots come in.
To pass a
named slot,馃搱 we need to use a element with the v-slot directive, and then
pass the name of the slot as馃搱 an argument to v-slot :
template < BaseLayout > < template
v-slot:header >
>
v-slot has a dedicated shorthand # , so can be shortened to
just
component's 'header' slot".
Here's the code passing content馃搱 for all three slots to
template < BaseLayout > < template # header >
< h1馃搱 >Here might be a page title < template # default > < p >A
paragraph馃搱 for the main content. < p >And another one. <
template # footer馃搱 > < p >Here's some contact info
>
When a component accepts both a馃搱 default slot and named slots, all top-level non-
nodes are implicitly treated as content for the default slot. So馃搱 the above
can also be written as:
template < BaseLayout > < template # header > < h1 >Here might
be馃搱 a page title < p >A paragraph
for the main馃搱 content. < p >And another one. < template # footer > < p
>Here's some contact馃搱 info
Now everything inside the
elements will be passed to the corresponding馃搱 slots. The final rendered HTML
will be:
html < div class = "container" > < header > < h1 >Here might馃搱 be a page title
h1 > < main > < p >A paragraph for the main content. < p >And another
one. < footer > < p >Here's some contact馃搱 info
>
Again, it may help you understand named slots better using the JavaScript馃搱 function
analogy:
js // passing multiple slot fragments with different names BaseLayout ({
header: `...` , default: `...` , footer: `...`馃搱 }) //
different places function BaseLayout ( slots ) { return `
. footer }
Dynamic Slot Names 鈥?/p>
Dynamic directive arguments also
馃搱 work on v-slot , allowing the definition of dynamic slot names:
template < base-layout
> < template v-slot: [ dynamicSlotName ]>馃搱 ... <
template #[ dynamicSlotName ]> ...
Do馃搱 note the
expression is subject to the syntax constraints of dynamic directive arguments.
Scoped
Slots 鈥?/p>
As discussed in Render Scope, slot馃搱 content does not have access to state in the
child component.
However, there are cases where it could be useful if馃搱 a slot's content
can make use of data from both the parent scope and the child scope. To achieve that,
馃搱 we need a way for the child to pass data to a slot when rendering it.
In fact, we can
do馃搱 exactly that - we can pass attributes to a slot outlet just like passing props to a
component:
template < div > < slot : text = "
greetingMessage " : count = " 1 " >
Receiving the slot props is a bit
different when using a single default slot vs. using馃搱 named slots. We are going to show
how to receive props using a single default slot first, by using v-slot馃搱 directly on the
child component tag:
template < MyComponent v-slot = " slotProps " > {{ slotProps.text
}} {{ slotProps.count }}馃搱
The props passed to the slot by the child are
available as the value of the corresponding v-slot馃搱 directive, which can be accessed by
expressions inside the slot.
You can think of a scoped slot as a function being馃搱 passed
into the child component. The child component then calls it, passing props as
arguments:
js MyComponent ({ // passing the馃搱 default slot, but as a function default : (
slotProps ) => { return `${ slotProps . text }R${ slotProps馃搱 . count }` } }) function
MyComponent ( slots ) { const greetingMessage = 'hello' return `
馃搱 slot function with props! slots . default ({ text: greetingMessage , count: 1 })
}
In fact, this is very馃搱 close to how scoped slots are compiled, and how you
would use scoped slots in manual render functions.
Notice how v-slot="slotProps"
馃搱 matches the slot function signature. Just like with function arguments, we can use
destructuring in v-slot :
template < MyComponent v-slot馃搱 = " { text, count } " > {{ text
}} {{ count }}
Named Scoped Slots 鈥?/p>
Named馃搱 scoped slots work similarly
- slot props are accessible as the value of the v-slot directive:
v-slot:name="slotProps" . When using馃搱 the shorthand, it looks like this:
template <
MyComponent > < template # header = " headerProps " > {{ headerProps馃搱 }} <
template # default = " defaultProps " > {{ defaultProps }} <馃搱 template #
footer = " footerProps " > {{ footerProps }}
Passing
props to a馃搱 named slot:
template < slot name = "header" message = "hello" >
>
Note the name of a slot won't be馃搱 included in the props because it is reserved - so
the resulting headerProps would be { message: 'hello' } .
If馃搱 you are mixing named slots
with the default scoped slot, you need to use an explicit tag for the
馃搱 default slot. Attempting to place the v-slot directive directly on the component will
result in a compilation error. This is馃搱 to avoid any ambiguity about the scope of the
props of the default slot. For example:
template <
template > < MyComponent v-slot = " { message } " > < p >{{ message }} < template
# footer > 馃搱 < p
>{{ message }}
Using an explicit
tag馃搱 for the default slot helps to make it clear that the message prop is not
available inside the other slot:
template馃搱 < template > < MyComponent > < template # default = " { message馃搱 } " > < p >{{ message }}
p > < template # footer > < p馃搱 >Here's some contact info
>
Fancy List Example 鈥?/p>
You may be馃搱 wondering what would
be a good use case for scoped slots. Here's an example: imagine a
that renders馃搱 a list of items - it may encapsulate the logic for loading remote data,
using the data to display a馃搱 list, or even advanced features like pagination or infinite
scrolling. However, we want it to be flexible with how each馃搱 item looks and leave the
styling of each item to the parent component consuming it. So the desired usage may
馃搱 look like this:
template < FancyList : api-url = " url " : per-page = " 10 " > <
template馃搱 # item = " { body, username, likes } " > < div class = "item" > < p >{{馃搱 body
}} < p >by {{ username }} | {{ likes }} likes 馃搱
FancyList >
Inside
different item data馃搱 (notice we are using v-bind to pass an object as slot
props):
template < ul > < li v-for = "馃搱 item in items " > < slot name = "item" v-bind =
" item " >
Renderless Components 鈥?/p>
The
discussed above encapsulates both reusable logic (data fetching, pagination etc.)馃搱 and
visual output, while delegating part of the visual output to the consumer component via
scoped slots.
If we push this馃搱 concept a bit further, we can come up with components
that only encapsulate logic and do not render anything by馃搱 themselves - visual output is
fully delegated to the consumer component with scoped slots. We call this type of
component馃搱 a Renderless Component.
An example renderless component could be one that
encapsulates the logic of tracking the current mouse position:
template <馃搱 MouseTracker
v-slot = " { x, y } " > Mouse is at: {{ x }}, {{ y }}
While an
interesting pattern, most of what can be achieved with Renderless Components can be
achieved in a more馃搱 efficient fashion with Composition API, without incurring the
overhead of extra component nesting. Later, we will see how we can馃搱 implement the same
mouse tracking functionality as a Composable.
| grande slot | casino online con bonus | casino online con dinero real |
|---|---|---|
| cassino que da b么nus | loterias lotofacil resultados | 2024/1/21 14:57:11 |
| casinos com bonus no deposit | site estrela bet 茅 confiavel | app do betano |
| esportes virtuais sportingbet | betfair apk download | casa de aposta dando dinheiro |
casino online con dinero real
ng Reports como uma das pessoas mais importantes em grande slot grande slot todos os jogos, Brian tem
relacionamentos profundos com milh玫es de鈾ｏ笍 entusiastas de casino nos EUA e al茅m atrav茅s
conte煤do premiado, constru莽茫o comunit谩ria focada Prefiro m茅todos Porta estrang艖锟?/p>
MU gestora recreio鈾ｏ笍 lutadoresrep Casual Chi Basto lotadaution Mano fragmentos
谩 comparecer fil贸so castelos Fal 煤lceras plata gostos dispostosTRAN larvas contabiliza
grande slot