Remove/address depth limitation of parseDateFields #522
Labels
backend
Issues related to the platform backend.
low priority
Low priority issues to be done eventually.
t-platform
Issues with this label are in the ownership of the platform team.
t-tooling
Issues with this label are in the ownership of the tooling team.
parseDateFields
traverses the provided JSON (used for Apify API responses) and converts certain fields to aDate
object. The traversion depth has been historically limited to 3, possibly to avoid cyclic dependencies and improve performance on large responses.This limitation is not communicated in any way, which might lead to weird surprises. We tried adding a
log.warning
but that led to log pollution as there are objects with arbitrary structure that went over the depth limit (most likely user data, data sets). Context here.Possible solutions:
Both are potential breaking changes.
This is currently not causing any issues and can be treated with low priority.
The text was updated successfully, but these errors were encountered: