Sending JSON payload to API in POST body

I have noticed that when I call my endpoints, like so:

import { endpoints } from "wildcard-api/client";

// in some async function
const response = await endpoints.saveNewCronJob({ newCronJob: editingCronJob });

I’m getting a request being sent out that looks like this:

http://localhost:8080/wildcard/saveNewCronJob/%5B%7B%22newCronJob%22%3A%7B%22id%22%3A%22%22%2C%22payloadType%22%3A%22TEXT%22%2C%22payload%22%3A%22%22%2C%22title%22%3A%22%22%2C%22timezone%22%3A%22Etc%2FGMT%22%2C%22endpointType%22%3A%22PUBSUB%22%2C%22endpoint%22%3A%22http%3A%2F%2Flocalhost%3A8080%2Ftest-cron-endpoint%22%2C%22enabled%22%3Afalse%2C%22description%22%3A%22%22%2C%22dateUpdated%22%3A%22json-s%3AtYpE%7CDate%7C2019-03-05T14%3A05%3A14.498Z%22%2C%22dateCreated%22%3A%22json-s%3AtYpE%7CDate%7C2019-03-05T14%3A05%3A14.498Z%22%2C%22crontab%22%3A%220%200%201%2F24%20*%20*%20*%22%7D%7D%5D

This indicates that the JSON is being serialised and set in the request url as a query string. While this is fine for small payloads, when things get large things might not work out too well (https://stackoverflow.com/questions/32763165/node-js-http-get-url-length-limitation).

[brillout]

There is nothing to check out 😃 Just update to v0.7.x and leave your code as it is. (Or simply keep v0.5.x.)

[brillout]

(I didn’t forget about this. I’m on vacation. Ttyl.)