Use CustomAutoField example with nested fields?

[Gervwyk]

I'm trying to implement the CustomAutoField example but having trouble with with nested fields since CustomAuto is not called for nested fields. Schema definitions like:

  'chartCursor.cursorColor':{
      type: String,
      label: 'Cursor color',
      defaultValue: '#888',
      uniforms: {
        fieldComponent: 'color'
      }
    }

and

  'bands.$.color':{
    type: String,
    label: 'Band color',
    defaultValue: '#888',
    uniforms: {
      fieldComponent: 'color'
    }
  }

Although works well for top level fields. Is there a better way to do this? or why is CustomAutoField not executed for nested fields?

I tested this for BS3 and antd theme.

[radekmie]

Well, it's not a bug, rather a new feature. Currently, NestField (and others) are simply importing nearest AutoField and using it - autoField prop being used only at the top level. There is no easy way to do it now, but I'll add it to the roadmap.

[radekmie]

Hey, @Gervwyk! It've been a while, but I've finally came to an idea. I'd introduce autoField option to connectField:

const CustomAuto = props => ...;
const CustomAutoField = connectField(CustomAuto, {autoField: true, ensureValue: false, includeInChain: false, initialValue: false});

It will mark this field as an AutoField (or it's replacement). This information will be passed down the context, so every field will know, what the current AutoField is. There's only one flaw...

<AutoField name="x">
    <Auto name="x" ...>
        <CustomAutoField name="x" ...>
            <CustomAuto name="x" ...>
                ...
            </CustomAuto>
        </CustomAutoField>
    </Auto>
</AutoField>

Yep, that's it. We can't replace usage of default AutoField with CustomAutoField, so it has to be nested.

What do you think?

[radekmie]

Other idea.
Introduce itemProps in NestField like in ListField. Then:

const schema = new SimpleSchema({
    tags: {
        type: [String],
        uniforms: {
            itemProps: {
                component: CustomAutoField
            }
        }
    }
});
// Then...
<AutoForm autoField={CustomAutoField} schema={schema} />

Will work as expected.

[Gervwyk]

Great! The second option seems easy to implement and fits well with current model. Thanks! Guess this one is finally resolved.