Skip to content

[fixes #1429] One to many associations were being removed without checking that the actual related object#1432

Merged
particlebanana merged 2 commits intobalderdashy:0.11.xfrom
luislobo:0.11.x
Feb 15, 2017
Merged

[fixes #1429] One to many associations were being removed without checking that the actual related object#1432
particlebanana merged 2 commits intobalderdashy:0.11.xfrom
luislobo:0.11.x

Conversation

@luislobo
Copy link
Contributor

One to many associations were being removed without checking that the actual related object is the same as the one the user is trying to remove.
The fix adds a condition to the update, so that it makes sure that the value matches.

One to many associations were being removed without checking that the actual related object is the same as the one the user is trying to remove.
The fix adds a condition to the update, so that it makes sure that the value matches.
@sailsbot
Copy link

Hi @luislobo! It looks like your pull request title doesn’t quite conform to our guidelines. Please edit the title so that it starts with [proposal], [patch], [fixes #], or [implements #]. Once you've fixed it, post a comment below (e.g. "ok, fixed!") and we'll take a look!

@luislobo luislobo changed the title Fixes issue reported in #1429 [fixes #1429] One to many associations were being removed without checking that the actual related object Jan 10, 2017
@particlebanana particlebanana merged commit 72a01eb into balderdashy:0.11.x Feb 15, 2017
@luislobo luislobo deleted the 0.11.x branch February 24, 2017 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants