Bugfix/js/deep nested arrays

[J3m5]

It modify the getField function in order to works with deeply nested arrays of objects and output a flat array of items.

This also helps interpreters to validate items without having to loop through nested arrays.

It removes the PROJECTED_FIELD const and its export as it's not needed anymore.

And it refactor the within interpreter by using testValueOrArray, the size one by removing the projected_field check and the all one by reordering the array check.

It also adds tests to be sure that getting and checking deeply nested arrays of objects works.

[stalniy]

Looks very good at first sight! Thank you very much!

I'll do a closer look tomorrow morning, today is a bit busy

[J3m5]

This PR introduce a bug with the size interpreter that is not caught with the current tests.
The reduce will concat arrays even if the arrays are the actual items that interpreters operates on.
Example:

    it('checks that at least one item from projected array satisfies condition', () => {
      const condition = new Field('size', 'items.a', 2)

      expect(interpret(condition, { items: [{ a: [2, 3] }, { a: [] }, {}] })).to.be.true
      expect(interpret(condition, { items: [5, 4] })).to.be.false
      expect(interpret(condition, { items: { a: [2, 3] } })).to.be.true

      expect(interpret(condition, { items: [{ a: [2, 3] }, { a: [4] }, {}] })).to.be.true
     // --> return false because the value is [2,3,4] and not [[2,3], [4]]
    })

[stalniy]

I’ll check how MongoDB works in case of checking size for deeply nested array props

[stalniy]

I fixed the issue. Thanks for pointing out!

[stalniy]

available in @ucast/js@2.2.1

[J3m5]

Great!