"Type[] | Null" produces incorrect rules

[mm-gmbd]

The following Bolt rules:

type Something {
  A: Boolean,
  B: Number[] | Null
}

path /path is Something {
  read() = true;
}

produce the following rules json:

{
  "rules": {
    "path": {
      ".validate": "newData.hasChildren(['A'])",
      "A": {
        ".validate": "newData.isBoolean()"
      },
      "B": {
        "$key1": {
          ".validate": "newData.isNumber()"
        },
        ".validate": "newData.val() == null"
      },
      "$other": {
        ".validate": "false"
      },
      ".read": "true"
    }
  }
}

Notice the rules for B. It correctly produces the map rule ensuring that all wildcarded children are numbers, but it also produces a rule for B itself, validation that newData.val() == null. This precludes me from being able to write anything at /path/B!

I think the desired behavior would be, when encountered with an Type[] | Null, it would not produce any validation at the level of Type.

[mm-gmbd]

It looks like the fix is to remove | Null entirely. I had thought this would make the .validate rules at path equivalent to the following:

"path": {
  ".validate": "newData.hasChildren(['A', 'B'])"
}

But it was smart enough to discard the 'B'. Still, probably would be less confusing to allow for Type[] | Null!

[mckoss]

Another test case:

path /x is String | Null;
path /y is String[];
path /z is String[] | Null;

produces:

{
  "rules": {
    "x": {
      ".validate": "newData.isString() || newData.val() == null"
    },
    "y": {
      "$key1": {
        ".validate": "newData.isString()"
      }
    },
    "z": {
      "$key1": {
        ".validate": "newData.isString()"
      },
      ".validate": "newData.val() == null"
    }
  }
}

[jacob-israel-turner]

I experienced this today. Commenting to follow the issue.

[YeomansIII]

Also having this issue, any progress on allowing Map | Null?

[nhim175]

I got the same issue today. Is there any work around for this?