Skip to content

Incompatibility introduced against legacy. #7

Description

@luismoyano

Hello! Wanted to report an incompatibility issue between two test cases I've found.

This is from @jwadhams' tests.json:

[
    {"map":[{"var":"integers"}, {"*":[{"var":""},2]}]},
    null,
    []
],
"or",
{
    "description": "Filter, map, all, none, and some (6)",
    "rule": {
      "map": [
        {
          "var": "integers"
        },
        {
          "*": [
            {
              "var": ""
            },
            2
          ]
        }
      ]
    },
    "data": null,
    "result": []
  },

and this is from this repo:

{
    "description": "Missing array returns error",
    "rule": {
        "none": [
            {"var": "missing"},
            {"<": [{"var": ""}, 0]}
        ]
    },
    "data": {},
    "error": {"type": "Invalid Arguments"}
},

Throwing an error here breaks backwards compatibility and according to the accepted proposals, this should not be happening. Can you clarify what should we be doing here? Shall we rewrite Missing array returns error? Or shall we deprecate it? Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions