This repository has been archived by the owner on Dec 12, 2021. It is now read-only.
JavaScript bug when the parent of a nested attribute is not in a "many" relationship. #19
Conversation
This file contains 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
added 2 commits
March 10, 2011 15:26
…n a "many" relationship. Example: project[tasks_attributes][assignments_attributes][1] instead of project[tasks_attributes][0][assignments_attributes][1]. Now the parent_ids array is never null.
|
Actually there is still a bug regarding this scenario: In a Root embeds_one Child embeds_many DeepChild, the name of a deeply nested field would be: root[child_attributes][deep_child_attributes][0][attribute] The javascript code responsible to fill the blueprint's parent's ids is broken, since it is always expecting an index after an /[a-z_]+_attributes/g |
|
I've created a new issue: #26 |
|
The asset "defaults.js" is not present in the asset pipeline. i got this error ..how to fix this error ..please explain this ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I found the bug while working with the gem on a MongoID project with a deeply nested form:
embeds_one -> embeds_many