Fix schema for tickets.json

[melnimr]

Add types to the value structure to adhere to the Singer specs.

[cmerrick]

Hi @melnimr, thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

[cmerrick]

You did it @melnimr!

Thank you for signing the Singer Contribution License Agreement.

[luandy64]

Looking at the docs, this PR would cause issues for people who have custom field values that are anything but strings (like numerics or arrays).

If you really need this in the schema, I recommend you fork this repo and run the tap yourself with the change.

[leo-schick]

@luandy64 You are right. Arrays do not work so this should be changed to:

"value": {
  "type":  ["null", "string", "array"],
  "items": {
    "type": ["null", "string"]
  }
}

It looks like that the API sends the numeric type as string.

Here are my used custom fields:

For the numeric field I got {"id": 360004765077, "value": "10517014"}.

The above definition worked for me with my custom fields setup shown above.