Receiving 'RangeError: invalid ISO 8601 string' via API for Numbers-only Strings
Author: obliqueRotationMethodCreated Sep 20, 2023Updated May 17, 2024
Hi,
running locally, I POST an pretty big JSON to the API. Some of my Strings in the JSON have Number-Characters only (userIDs). When opening the link, console is showing a lot of 'RangeError: invalid ISO 8601 string: 12345' - warnings/ errors. It takes up to one minute to open the link, npm service is running on 100% CPU usage
On the site, I see that the program interprets my Number-Strings as Date-Objects (string/datetime/rfc3339). Example: {"lastModifiedBy": "12345678"}
My actual date strings in there are ISO 8601-formated. Maybe a workaround could be to add a parameter to state the date format. To let the backend know which Strings to parse as dates and leave the rest as normal text?
Source: triggerdotdev/jsonhero-web