You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
if both sides of relationship are new belongs_to side may not get reported back #173
everything gets saved but in the return data the new instance of Foo will not be reported, and thus bar.foo will not have an id, and will look like its still "new". If you then bar.save again, another copy of Foo gets created.
There are two reasons the data may not get reported:
There is not policy for the Foo, so no attributes are returned.
Because of the order of saves on the server, what happens is the new instances of foo and bar are created, and linked, but then bar is saved first, causing an automatic save of foo. This makes the system think foo never changed, and thus no data is reported.
Activity
testing fix for #173
catmando commentedon Apr 20, 2019
There are two reasons the data may not get reported:
further work on #173
fixed regression and other issues raised by #173
continuing to work correct solution to #173
one more time to fix #173 and duplicate dispatches
testing fix for hyperstack-org#173
further work on hyperstack-org#173
fixed regression and other issues raised by hyperstack-org#173
continuing to work correct solution to hyperstack-org#173
one more time to fix hyperstack-org#173 and duplicate dispatches