Trying to fix nested problems with a has_one relation#137
Open
hposca wants to merge 1 commit intoVizir:masterfrom
hposca:has_one_nested
Open
Trying to fix nested problems with a has_one relation#137hposca wants to merge 1 commit intoVizir:masterfrom hposca:has_one_nested
hposca wants to merge 1 commit intoVizir:masterfrom
hposca:has_one_nested
Conversation
The call to "build_#{field.name}" when we have a has_one relationship
actually caused the object to be overwritten. So every time the view was
opened in 'edit' the old data disappeared.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The call to "build_#{field.name}" when we have a has_one relationship
actually caused the object to be overwritten. So every time the view was
opened in 'edit' the old data disappeared.