Bug description
With remove_empty_nodes: true in the blueprint, saving an entry with cmd+s makes Bard sets display the next set's values. Saving once more writes those wrong values to the file.
How to reproduce
- Clone https://github.com/helloiamlukas/bard-save-bug
- Open /cp/collections/articles/entries/repro-entry
- Click into the Bard editor (an empty paragraph, not into a set)
- Press cmd+s
- The first two sets will be rendered wrong now (the file is still okay!)
- Press cmd+s again
- The sets are rendered wrong again, but this time also the modified sets are written to the file
Logs
Environment
Laravel Version: 13.31.0
PHP Version: 8.5.8
Composer Version: 2.10.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 0
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.32.0 Solo
Installation
Starter Kit using via CLI
Additional details
No response
Bug description
With
remove_empty_nodes: truein the blueprint, saving an entry with cmd+s makes Bard sets display the next set's values. Saving once more writes those wrong values to the file.How to reproduce
Logs
Environment
Installation
Starter Kit using via CLI
Additional details
No response