Closed marcorieser closed 6 months ago
Thank you very much for this!
I may end up forcing withEvents(true)
for oneToMany to ensure the down-stream entries get updated. I've identified the issue with the failing cases when withEvents(true)
is enabled. I'll be looking to do a release either this evening or sometime tomorrow after taking a look at a few other open issues 🙂
Glad you found the issue. Thank you so much.
Another edge case cropped up that is proving to be challenging. Will keep you updated 👍
Alright, I've got all but this one working now "In an author entry, assign a book already assigned to another author" (withEvents = false). I'll do some thinking on if that can be reasonably supported without cascading events.
I'm going to sit on this one overnight and work on some test coverage before pushing it out, though
As soon as I walked away I thought of a solution. All of your scenarios will now work, regardless of the withEvents
setting, with expanded test coverage. Should be good to go as of 2.1.5
Thanks again for putting together such a great sample repo!
Just gave it a shot and everything works like a charm. Tried to be a bit mean by mix and match cases from above. Everything perfect. Thank you!
Issue
I have some weird sync problems when using
oneToMany()
.Personally I do not need events to be triggering but since there are issues (https://github.com/Stillat/relationships/issues/32) when they are enabled, I tested my cases with them enabled too.
Reproduction
withEvents(false)
)AppServiceProvider::boot()
Test Cases (
withEvents(false)
)