"Nullness" of a JSON null is lost while iterating using formap about murex HOT 4 CLOSED

Good spot.

The parser for object creator was a little slapdash. I'm pretty sure I wrote that code wrapped under a blanket while fighting off covid. Which also explains why the tests aren't thorough enough.

I'm going to merge the changes I have currently and will rewrite the object creator parser for a new release.

from murex.

Looks like you've uncovered not one, but two bugs in the parser.

null bareword parsed as string:

» %{ "foo": null }
{
    "foo": "null"
}

variables are tokenised for is-null parameters

» $foo = "bar"
» is-null foo
foo: defined and not null
» is-null $foo
bar: undefined or null

Both of these are trivially fixable so I'll get an update pushed to develop shortly

from murex.

@tiymat pushed a fix to develop. I'll probably put this live in the next day or two because it's a low impact change.

from murex.

In testing the develop version (5.3.7000) I noticed a potentially-related issue.

In JSON objects constructed with %{} syntax, is-null seems to interpret empty strings as nulls, contradicting the documentation which says "Zero length strings [...] are all not null."

tmp » cat test.mx
#!/usr/bin/murex

%{ "foo": "" } -> formap key value {
	if { is-null value } then {
		out "value is null"
	} else {
		out "value is NOT null"
	}
}
tmp » ./test.mx
value is null

Edit: I guess the issue isn't with is-null itself but rather how the JSON object is being parsed/constructed.

~ » %{ "foo": '' }
{
    "foo": null
}

from murex.