Closed donalmurtagh closed 7 years ago
Yes this was a fix for a bunch of name related issues both in arrays when fields had the same property names, radio issues and problems when the page had multiple form with fields named the same. I've tagged needs documentation, thanks :)
This can now be tracked in the migration doc issue
I'm not sure when exactly this changed, but prior to upgrading to the latest alpha, I was generating field names like this in my templates:
The latest templates seem to recommend using the following instead
I changed my templates to use the new field names and in the case of one particular field inside an array, this changes the field name from
to
I think this should be mentioned in the migration guide, because there may be other parts of the application that rely on the old names.
More importantly, I discovered that the old names don't work for fields inside arrays
@json-schema-form/angular-schema-form-lead