Skip to content

Improve separation of concerns in Request and RequestOptions #3086

@janbuchar

Description

@janbuchar
  • The current Request and RequestOptions conflate functionality relevant to Crawlee in general with Apify-specific functionality
  • We might need to introduce additional classes to make the distinction clearer between what is used for various storages and what is a user-facing abstraction
  • Request.payload should support binary buffers 🙂

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions