Describe the bug 📝
Clipper onAfterDelete fires onBeforeDelete - expected state is wrong at the time of the call. onAfterDelete is expected to have the list already updated, the entry removed, size being up to date. Currently it is not, the removed entry is still there.
|
this.list.onBeforeDelete.add(({ value: plane }) => { |
|
if (!plane.world.renderer) { |
|
throw new Error("Renderer not found for this plane's world!"); |
|
} |
|
plane.world.renderer.setPlane(false, plane.three); |
|
plane.dispose(); |
|
this.updateMaterialsAndPlanes(); |
|
|
|
this.onAfterDelete.trigger(plane); |
|
}); |
Reproduction ▶️
No response
Steps to reproduce 🔢
No response
System Info 💻
Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅
Describe the bug 📝
Clipper
onAfterDeletefiresonBeforeDelete- expected state is wrong at the time of the call.onAfterDeleteis expected to have the list already updated, the entry removed,sizebeing up to date. Currently it is not, the removed entry is still there.engine_components/packages/core/src/core/Clipper/index.ts
Lines 251 to 260 in 1d8ca36
Reproduction▶️
No response
Steps to reproduce 🔢
No response
System Info 💻
Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅