Skip to content

BasicCrawler.export_to should redefine the key and content_type parameters #211

@janbuchar

Description

@janbuchar
  • the key parameter is mandatory, but the user has to browse the source code or wait for a crash to know that
    • turns out LSP tells you about that... still, the docs should probably contain mandatory parameters
  • going blind, I tried passing foo.csv to key and got a file called foo.csv.json, which we may also want to handle somehow
  • we probably want to replace this with export_data, analogous with TS
  • add get_data while we`re at it

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request.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