Array minItems not populated when default value is specified

[straygar]

Prerequisites

• I have searched the existing issues
• I understand that providing a SSCCE example is tremendously useful to the maintainers.
• I have read the documentation
• Ideally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.

What theme are you using?

core

Version

5.8.0

Current Behavior

Given a schema:

{
  "type": "object",
  "required": [
    "myProp"
  ],
  "properties": {
    "myProp": {
      "type": "array",
      "items": {
        "type": "string",
        "default": "abc"
      },
      "minItems": 1
    }
  }
}

And a form:

<Form
  schema={formSchema}
  experimental_defaultFormStateBehavior={{
    emptyObjectFields: 'populateRequiredDefaults',
    arrayMinItems: 'populate',
  }}
>

myProp is an empty array in the form.

Expected Behavior

myProp is prepopulated, i.e.:

{
  "myProp": [
    "abc"
  ]
}

Steps To Reproduce

1. Open playground link
2. Observe that the array is not prepopulated with "abc" as expected

Environment

- OS:
- Node:
- npm:

Anything else?

No response

[nickgros]

@straygar It will work if you set experimental_defaultFormStateBehavior.emptyObjectFields to 'populateAllDefaults'. populateRequiredDefaults won't work because the field is not an object or a primitive.

I'm not sure if this is a bug--it seems like this may be an edge case where the combination of these two options should work how you expect? Or maybe we need to extend the API to explicitly handle this type of scenario. I defer to @heath-freenome and @RPiAwesomeness

[straygar]

If I understand correctly, because emptyObjectFields does not cover arrays, myProp is never visited? And since it is never visited, the arrayMinItems: 'populate' does nothing?

[heath-freenome]

@straygar Ok, you found another bug in our imperfect defaulting code. I tried using this alternative approach in the playground but that didn't work either. Given how busy the few of us who maintain this repo are, your best bet for getting this fixed is to figure out where the problem is and then pushing a PR. Is this something you are willing to try?