clasp run returns 'No response' when Apps Script function returns 0

[joccing]

(Note: Non-breaking issues are likely not to be prioritized. Please consider a PR in addition to your issue)

Expected Behavior

When running an Apps Script function, clasp run should return whatever the function returns.

Actual Behavior

When the function returns a 0, clasp run returns 'No response', and the correct output at other values. To force the 0 to be returned, you need to return the type cast String(output).

Steps to Reproduce the Problem

1. Create an apps script function

function test() {
return 0;
}

2. do clasp run test
   No response.

3. Change to

function test() {
return 1;
}

4. do clasp run test
   1

5. Change to

function test() {
return String(0);
}

6. do clasp run test
   0

Specifications

• Node version (node -v): 13.8.0
• Version (clasp -v): 2.3.0
• OS (Mac): 10.15.4

[joccing]

Hi Clasp Developer,

May i know if there is a solution to this problem? or is it expected behaviour.

[leeyspaul]

I'm getting the same error with the production version. When it's a string it returns 0 when it's int it returns No Response.

But when I build with npm run build after uninstalling it globally it returns the correct response (haven't investigated yet).

$ clasp run testStrInt
(node:48234) ExperimentalWarning: The fs.promises API is experimental
Running in dev mode.
0

$ clasp run testInt
(node:48232) ExperimentalWarning: The fs.promises API is experimental
Running in dev mode.
No response.

Node version: v10.10.0
Clasp version: 2.3.0

[atimangel]

function that you run is not return anything.
if your function return something it will print on your terminal.

[sqrrrl]

Fixed in next release of 3.x (alpha). Issue was any falsey value was interpreted as no result. Updated to only output no result if the return value is undefined.