https://github.com/codewithdennis/filament-v4-repeater-increment-issue
https://github.com/codewithdennis/filament-v4-repeater-increment-issue
Last synced: 11 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/codewithdennis/filament-v4-repeater-increment-issue
- Owner: CodeWithDennis
- Created: 2025-06-13T13:37:31.000Z (12 days ago)
- Default Branch: main
- Last Pushed: 2025-06-13T13:39:30.000Z (12 days ago)
- Last Synced: 2025-06-13T14:46:39.522Z (12 days ago)
- Language: Blade
- Size: 1.38 MB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Bug Report: Table Repeater id Field Behavior in V4
### When adding an id field to a repeater and saving the form, it doesn't preserve the original id values. Instead of updating existing records, it updates them with new ids, essentially overwriting the existing entries with different primary keys. This does not happen in V3.
# Installation
```bash
git clone [email protected]:CodeWithDennis/filament-v4-repeater-increment-issue.git
cd filament-v4-repeater-increment-issue
composer install
npm install
npm run build
cp .env.example .env
php artisan key:generate
php artisan migrate
php artisan db:seed
```
## What I Observed
**When including an id field in the table repeater (whether it's a disabled text field or a regular TextEntry):**
- Existing entries get new id values on save, instead of keeping their original ones.
- The id value is not displayed correctly in the TextEntry field. (Possibly a separate issue?)
- Removing disabled from the id field seems to fix the issue, but this is not a viable solution as it should be a read-only field.
## How to Reproduce
- Login to the admin panel. (Login credentials are prefilled in the form.)
- Go to items
- Click on a random item
- Edit the item
- Save the item and see the id field increments instead of preserving the original id values.