Zero value being stored as null

[bpj]

@Apple

You could access it like this:

$_ENV.SEND_METRICS.default(1)

You could easily just reverse the statement:

$_ENV.DO_NOT_SEND_METRICS.default(0)

and use it as a flag to stop sending metrics if set. The way not set or set to 0 will send metrics and 1 will prevent sending them

What we’re talking about is the behaviour of 1 and 0 as true and false. This is standard JavaScript (and pretty much every programming language I have ever come across). Whether or not you explicitly defined it or not, using 0 will evaluate as false.

In terms of documentation - The default formatter has a simple task:
if the value evaluates to false (undefined, empty, 0, false) then use the value set in the parentheses

There is a slight caveat client-side where empty strings are not treated as false - discussed here:

Default - different behaviour for SC to Client-Side

Is the data binding default function meant to work the same for both SC (in my case PHP) and client-side? I’m finding that the behaviour for empty strings (not NULL) is different: Server Connect treats an empty string as something that would trigger the default value however, client-side formatter seems to leave it as an empty string. e.g. imagine a SC returns two values firstname = 'John' preferredname = 'Johnny' I use preferredname.default(firstname) to show the preferred name if presen…