feat: Customizing CSS selectors can sometimes cause web crawlers to fail #153
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When crawling a webpage, if a custom CSS selector is selected, but the initial page does not have a suitable CSS selection object, it will cause the crawler to fail. If a custom CSS selector is not used, the truly valuable page (which can filter out a lot of useless information through the CSS selector) will have a lot more useless information, such as the "homepage". So this submission can be used when a custom CSS selector is available, and when it is not possible, use "body" as the CSS selector