-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposed fix for issue 590 #672
Conversation
Reset keyRedaction variable so that the parent's keyRedaction will not be carried onto its children which used to cause the key to be an empty array inside the ngModel builder.
Thanks @elbunuelo, I have a test in PR 652 that currently fails due to this issue (#590). So this PR should make my test pass! |
@joelwkent I'm glad to read it! Now I just have to work out why aren't the tests passing |
@elbunuelo there are some tests failing because of styles not being set, I think David said those tests should be moved to the decorators instead anyway, but I havent had a chance to fix it yet. Nice PR, glad to see the template properly filled in, I will fix it's styling today, nice PR :) |
@joelwkent did you get a chance to see if this resolved your test issue? |
Yes, happy to confirm this PR fixes the issue in the test I have added in the arrayIndices PR. |
Description
Fixes issue 590, which describes a bug that appears when you're using nested arrays.
The described bug causes element values in the second nesting level to appear as [Object object].
Fixes Related issues
json-schema-form/angular-schema-form-bootstrap#9
Checklist
@json-schema-form/angular-schema-form-lead
Reset keyRedaction variable so that the parent's keyRedaction will not be carried onto its children which used to cause the key to be an empty array inside the ngModel builder.