[8.x] Expose the view component stack and keep full components on stack #36512
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an alternative approach to #36472. This PR includes two changes:
View::getComponentStack()
so that components can access the stack during render (for example, to find their parents)startComponent()
so that when components are accessed from the stack you have access to more than just their resolved viewIt turns out that
CompilesComponents::compileClassComponentOpening
will need to be changed for this to work, since right now we're only passing$component->resolveView()
rather than the whole component. But this approach does mean that there's not a need to track child components, and adds support for accessing components that are not directly next to each other on the stack (like my instant search example).