Binding Data for integers is inconsistent.

[brendandburns]

Investigative information

Please provide the following:
N/A - this issue is reproducible locally.

Repro steps

Provide the steps required to reproduce the problem:

Run the following Typescript function:

import { AzureFunction, Context, HttpRequest } from "@azure/functions"

const httpTrigger: AzureFunction = async function (context: Context, req: HttpRequest): Promise<void> {
    context.res = {
        body:context.bindingData
    }
}

With the following function.json

{
  "bindings": [
    {
      "authLevel": "anonymous",
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "route": "periods/{id}",
      "methods": [
        "get"
      ]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "res"
    }
  ],
  "scriptFile": "../dist/TestFunc/index.js"
}

Run func start

Hit the URL with 0 as the parameter:

curl <function-url>/api/periods/0

Output is:

{
  "invocationId": <hash>,
  "id": {
    "string": "0",
    "data": "string"
  },
  ....
}

Hit the URL with 1 as the parameter

curl <function-url>/api/periods/1

Output is:

{
  "invocationId": <hash>,
  "id":  1
...
}

Expected behavior

Format should be the same no matter what value is passed in.

Actual behavior

Format is integer literal for non-zero values (id: 1) and an object ({ ... }) for zero values.

Known workarounds

You can detect and respond in code, but that is ugly.

Related information

Provide any related information

• Programming language used: Typescript
• Links to source: Above
• Bindings used: Above

Source

import { AzureFunction, Context, HttpRequest } from "@azure/functions"

const httpTrigger: AzureFunction = async function (context: Context, req: HttpRequest): Promise<void> {
    context.res = {
        body:context.bindingData
    }
}

[anthonychu]

Thanks @brendandburns. This is an interesting behavior and we'll investigate.

We recommend that you use req.params to access routing parameters. The behavior should be consistent in that case.

[mhoeger]

I'm not sure where exactly something is going wrong, but it seems very likely that in some code path, we aren't explicitly checking for value == null. Related: #364

This is a breaking change we need to make with V4.

[ejizba]

Fixed in #414