Support for @aware in Blade Component Class

[jardakotesovec]

Context why I am asking for the feature

We are hoping to adopt Blade templating system in our OJS opensource software publishing software.

As part of that process I was hoping to create good components abstraction, inspired by headless components (like reka-ui). To abstract out correct semantic html, some business logic and data extraction to these components. And let developer just focus on styling and organising the components - to be able to create very custom themes.

While working on good api design, I have run into the problem, where I am not unable to use aware inside component class to be able to access the data in the class itself.

Example when this would be useful
In this case I am able to access the $author in x-author.full-name, because I don't need component class. But for x-author.affiliations I need to be able to expose the array of affiliations on the $component and for that I need the class and need to be able to access $author in that class. Currently only way to achieve this is to pass the $author again to the x-author.affiliations, which would be very confusing, why some components needs it and some don't.

        <x-author :author="$author">
            <x-author.full-name />
            <x-author.affiliations>
                @foreach($component->affiliations as $affiliation)
                    <x-author.affiliation :affiliation="$affiliation">
                        <x-author.affiliation.name />
                        <x-author.affiliation.ror />
                    </x-author.affiliation>
                @endforeach
            </x-author.affiliations>
     <x-author>

Proposed feature
Bring the $aware functionality to the class components. My understanding is that this option was considered originally when this feature was worked on - #39100 (comment) . And @taylorotwell decided not to include it at that time. And I am hoping this could be reconsidered to allow some of these abstractions.

To me this came as big surprise while working on this - that I can access it only from child view. As I would consider component as part of the "child component".

Would PR for this addition be accepted?

Thank you for the feedback!

[Nabil-nl]

That’s a very solid use case. Right now $aware only works inside the Blade view itself, which indeed forces you to re-pass data when you want to expose it from the class.
I can see how, in your example with , it feels inconsistent that x-author.full-name can directly access $author, but x-author.affiliations needs you to pass $author again just so the class can hydrate its own properties.
Bringing $aware to class components would definitely make abstractions cleaner especially for headless component patterns where the class is meant to handle business logic while the Blade just focuses on markup/styling. It would also reduce boilerplate and improve DX.
The only thing I’d be curious about is whether there are technical limitations (like lifecycle order of how data is resolved for class components) that originally made it harder to support. But if that’s solvable, I think this proposal would be a very welcome improvement.
If you’re willing to open a PR, I’d imagine it could at least start the discussion again and see whether Taylor and the core team feel it’s the right time to bring it back.

[jardakotesovec]

@Nabil-nl Thank you for the feedback.

@inxilpro Hi Chris, any chance you remember when you worked on the original aware feature - how feasible would be to support accessing parent prop directly in the component class?