filamentphp/filament

Broken Repeater delete when a child component has lazy prop.

Open

#19,575 opened on Mar 27, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)PHP (4,162 forks)batch import
bughelp wantedmedium priorityunconfirmed

Repository metrics

Stars
 (30,736 stars)
PR merge metrics
 (Avg merge 2d 15h) (72 merged PRs in 30d)

Description

Package

filament/filament

Package Version

v4.9.1

Laravel Version

v12.56.0

Livewire Version

v3.7.12

PHP Version

8.5.0

Problem description

When you delete an entry/record from a Repeater which has a child component that is marked as lazy, the deletion will not work.

Expected behavior

The item to be deleted upon save.

Steps to reproduce

  • setup reproduction repository (clone, migrate database, create a user)
  • login
  • Edit user
  • add 1 or more options to options repeater
  • save form (works)
  • delete an option (correctly removes the item from frontend view)
  • save form again
  • witness the deleted item reappear.

Reproduction repository (issue will be closed if this is not valid)

https://github.com/tvercruysse/filament-broken-repeater-delete-lazy-item

Relevant log output

Contributor guide

Research direction
Investigate the Livewire repeater component's delete method and how lazy child components affect the removal logic. Check if the lazy prop causes the child component to skip updates or reinitialize improperly, preventing deletion from persisting.
Tech stack
phplaravel
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PHPLaravelGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65