You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we try to parse all response fields ending with At as dates, even in user-supplied data in dataset items, requests in queues etc. This leads to undesired behavior when the data is not parseable as dates.
For example, this request
{"url": "http://example.com","userData": {"postedAt": "30+ days ago",},}
Currently, we try to parse all response fields ending with
At
as dates, even in user-supplied data in dataset items, requests in queues etc. This leads to undesired behavior when the data is not parseable as dates.For example, this request
would get parsed as
and there would be no way to get to the actual
postedAt
field contents.We could either:
The text was updated successfully, but these errors were encountered: