Skip to content

Remove/address depth limitation of parseDateFields #522

Open
@tobice

Description

@tobice

parseDateFields traverses the provided JSON (used for Apify API responses) and converts certain fields to a Date 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:

  • Remove the limitation
  • Stop parsing objects with arbitrary structure (user data, data sets)

Both are potential breaking changes.

This is currently not causing any issues and can be treated with low priority.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendIssues related to the platform backend.low priorityLow priority issues to be done eventually.t-platformIssues with this label are in the ownership of the platform team.t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions