Open jwmann opened 5 years ago
A temporary solution is to replace filters[${index}]name
with filters.${index}.name
, I'm still thinking about a better way to support dynamic fields.
If you have any ideas, feel free to join the discussion.
The workaround you suggested could sorta work but not quite what I was looking for.
I think you'd need to implement a sort've getter/setter function.
If we use rc-form
as an example, they use these kinds of getter/setters
Is there a way to use nested fields? An example would be an array of fields that nests under a common key.
In the above example, I've created an array with 1 object inside and set it to the
filters
key. By setting the name to use the index of the filters themselves, I could essentially link it to the correct field.However in practise it just make a new key called "filters[0]name" which I suppose is expected. Just wondering if this Form is capable of nested fields and I'm doing it wrong or perhaps this may be a feature request.