Use a named slot to separate attribute merges

[Jade-GG]

Follow-up to #23

This update lets us do magics like this:

<x-rapidez-ct::input.radio v-model="some_variable">
    <x-slot:wrapper class="font-bold">
        label text
    </x-slot:wrapper>
</x-rapidez-ct::input.radio>

Of course, you can still do:

<x-rapidez-ct::input.radio v-model="some_variable">
    label text
</x-rapidez-ct::input.radio>

or even:

<x-rapidez-ct::input.radio v-model="some_variable">
    <x-slot:wrapper class="font-bold"></x-slot:wrapper>
    label text
</x-rapidez-ct::input.radio>

This seems like the nicest approach to me.

[JimmyHoenderdaal]

👍

[Jade-GG]

Do we want this refactored on all the input components (where it makes sense)? There's quite a bit of $attributes->only vs $attributes->except and for internal consistency it might be nice.

[royduin]

Yeah, that would be nice!

[jordythevulder]

Why do you use after psuedo elements when you just can create a new <div?

[Jade-GG]

Not sure, that isn't my code @JimmyHoenderdaal 😇

[JimmyHoenderdaal]

Why do you use after psuedo elements when you just can create a new <div?

this is because you would otherwise need group-peer-checked to toggle, we can't assume people are using that since it isn't in rapidez by default

[royduin]

So now we've this: laravel/framework#48039 🚀 maybe wait for the release of that and add it as minimal requirement in the composer.json?