[Blade] graceful failing of components

[marvinosswald]

Motivation

If i have a list of things to show on a page i don't want the entire list to fail just because one item doesn't work. I could solve this by using lazy livewire components or js rendered solutions, but think this would be nice to just have in blade as the added complexity of both other solutions isn't necessary at all.

Scenario:

I have a grid of cards being build like this:

<div class="grid">
@foreach($cards as $card)
  <x-card :card="$card" />
@endforeach
</div>

now if one of these x-card components fails for any reason it's going to take down the entire site it is being rendered on with it.

Idea:

Have a "graceful fail" mode for Blade, which would result in the one card not rendering but the rest untouched. The exception still should be logged and everything but i see no reason why it should fail the entire rendering process. I think logical boundaries to draw would be components and partials.

Details

Relevant code for gracefully failing Blade components:

framework/src/Illuminate/View/Concerns/ManagesComponents.php

Lines 86 to 108 in cfe5f84

	public function renderComponent()
	{
	$view = array_pop($this->componentStack);
	$this->currentComponentData = array_merge(
	$previousComponentData = $this->currentComponentData,
	$data = $this->componentData()
	);
	try {
	$view = value($view, $data);
	if ($view instanceof View) {
	return $view->with($data)->render();
	} elseif ($view instanceof Htmlable) {
	return $view->toHtml();
	} else {
	return $this->make($view, $data)->render();
	}
	} finally {
	$this->currentComponentData = $previousComponentData;
	}
	}

Thinkable features for this:

• Gracefully failing components
• Gracefully failing partials
• (2nd stage) Creating a default error template which gets used instead
  • this could be overwritable in userland
• (2nd stage) Config to switch between nothing being rendered or an error template