crawling

At the moment, ItemLoader(response=response) fails if response is not a TextResponse instance.

Passing a binary response can still be useful, though. For example, to allow processors to access the response from their loader context, and hence be able to report the source URL (response.url) when reporting input issues.

It's been awhile since I updated e2e tests and there are some of them that are filing (most of them are related to examples).

Also, we need to add e2e tests that cover headers and cookies for both drivers.

Main examples at Apify SDK webpage, Github repo and CLI templates should demonstrate how to manipulate with DOM and retrieve data from it.

Also add one example of scraping with Apify SDK + jQuery to https://sdk.apify.com/docs/examples/basiccrawler

Feedback from: https://medium.com/better-programming/do-i-need-python-scrapy-to-build-a-web-scraper-7cc7cac2081d

I lost an hour trying to make

Currently, in master, the logs are stored in a non-optional manner.

I think a good improvement for this would be to make the file logging optional, as not everyone has log rotation configured or needs logging (especially ad-hoc users).

Mentioned first here: elixir-crawly/crawly#155 (comment)

Some improvements i can think of is:

• optional switch to enabl

We have different mixins in spidermon/contrib/monitors/mixins directory, but no documentation.