Skip to content

[FEATURE] Ignore empty result #195

Description

@mhalano

Is your feature request related to a problem? Please describe.
There are some websites whose content is flaky, so my results, after filtering, sometimes disappear and go back later. I would like to not consider when the result is empty, because I know it's not empty; just the website is flaky and will back in a posterior run.

Describe the solution you'd like.
An option like ignore_empty_result that checks if the result, always after the filtering being done, is empty (or just spaces) and didn't show as a change and neither saves the result, so in the database there will always be a non-empty last result.

Describe alternatives you've considered.
In the previous issues we were tweaking the additions_only, but it even ignoring the empty result and not showing as a change; the other run when the correct value is present still shows as a change.

Additional context.
Continuation of #169

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions