var operator doesn't like to handle decimal points

[dirkd70]

Values with periods are not matched with the "var" operator

rule: { "var": "1.2TB"}
data: { "1.2TB": 1, "2.4TB":2,"4.8TB":4 }
output: null

Works fine with == operator (and floating point numerical comparisons in general)

[loganhersh]

@dirkd70 I believe this is intentional. A common use case is to use . in the var path to access properties that are deeper than the top-level. If your data object looked like this it would probably work:

{
    "1": {
        "2TB": 1
    },
    "2": {
        "4TB": 2
    },
    "4": {
        "8TB": 4
    }
}

Obviously that's not your intention, but I can't imagine the current behavior will change because it would likely break use cases that are much more common than yours. I would generally consider it bad practice to use . in object keys.

Could you possibly change the keys to whole GB numbers instead so that you can eliminate the . in the keys?

[dirkd70]

I just illustrated using a simple example.
My current use case, I want to provide a match of a list of package/driver/firmware versions (e.g. kernel-5.14.0-427.65.1.el9_4.x86_64)

To work around this, I've just substituted the period with an underscore for both the value and list entries.

[TotalTechGeek]

Hey there, this was a primary motivator for the JSON Logic Community project to consider moving towards an alternative operator without the pathing syntax: https://github.com/orgs/json-logic/discussions/18

This syntax is available in json-logic-engine, but to build this into json-logic-js, you could use the following

logic.add_operation('val', function () {
  let data = this
  for (let i = 0; i < arguments.length; i++) {
    if (data === null || data === undefined) return null
    data = data[arguments[i]]
  }
  if (data === undefined) return null
  return data
})

Which would mean you could use

{ "val": "1.2TB" }

Without issue.

And to access nested properties,

{ "val": ["1.2TB", "Specs"] }