-
Notifications
You must be signed in to change notification settings - Fork 505
JavaScript bug when the parent of a deeply nested attribute is not in a "many" relationship. #26
Comments
Thanks for reporting this. I'll mark this to be fixed in the code. |
I pulled in the change from @eljuanchosf which should fix this problem. Let me know if it doesn't and I'll re-open. |
This problem is still happening for me |
@garrettlancaster Could you please push a test application reproducing your issue? |
Sure thing, here is the link: https://github.com/garrettlancaster/nested_form_failing. Let me know if you need anything else. |
Oh, and make sure to add at least two gifts. It works if you only add one. Overview of the contrived example: |
@garrettlancaster Thanks! I'll take a look. |
It happens to me too. |
any progress on this? |
Es cierto, debería, pero por algún motivo no sucede lo que debería Habría que identificar en donde se produce el cambio.
Abrazo! On Sat 23 Apr 2011 02:06:28 PM ART, ryanb wrote:
Mis mejores deseos, Juan Pablo |
The fix proposed in #19 is not complete:
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 ex:
root[child_attributes][0][deep_child_attributes][0][attribute]
The text was updated successfully, but these errors were encountered: