Mustache tags null values are returning "null" strings again

[govvin]

What happened?

I am familiar with this issue which was resolved back in 2019, but there seems to have been a regression.

I haven't been using it in projects until yesterday, and I found out that mustache tags encountering null values are returning "null" strings again.

Steps to reproduce

For example, adding recommended tags in your task instructions, like:

`man_made=bridge`
`name=`{{name}}
`alt_name=`{{alt_name}}

may return something like, null values return "null" strings.

man_made=bridge
name=Xyz Bridge
alt_name=null

rather than the previous behavior I expected:

man_made=bridge
name=Xyz Bridge
alt_name=

Environment

Firefox, Vivaldi

Additional information

No response

[govvin]

Hello. I just checked how this fix is working in this challenge, but it doesn't appear to have made any difference.

I tried using it the following ways:

`key={{value}}`
`key=`{{value}}

and in both cases, I still get

key=null

[CollinBeczak]

It's because the backend is set up to turn the properies values into strings... so you get "null" instead of a null vallue. For now i think the best course of action would be to check if property == "null", and if so return "" (nothing).

But in my mind there is a data issue, i just dont want to fix it at the moment, and im not sure if fixing it will break any maproulette plugins or reports people have or something. Something I will keep in mind tho in future dev.

[govvin]

Can you suggest any workaround for this, for now?

[CollinBeczak]

I'm not sure if this workaround covers all the bases, but one workaround is to change all occurrences of

properties: { "alt_name": null }

to

properties: { "alt_name": "" }

in your geojson.

I just made a new challenge, not sure how you would go about fixing this on an existing challenge.

[govvin]

That's a good workaround. I confirm it works.