Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EXTRACTION STOP CONDITIONS (Part II): As Dan, I want a way to define when an extraction should stop so that the harvest does not run forever #53

Merged
merged 13 commits into from
Jan 9, 2024

Conversation

richardmatthewsdev
Copy link
Contributor

@richardmatthewsdev richardmatthewsdev commented Dec 20, 2023

Acceptance Criteria

  • User can define stop conditions when building the extraction

Notes

  • Should it stop if the record_selector finds no records?

Screenshot 2024-01-09 at 11 06 00 AM

@richardmatthewsdev richardmatthewsdev changed the title feat(stop_conditions_2): Add new Stop Condition model and association… EXTRACTION STOP CONDITIONS (Part II): As Dan, I want a way to define when an extraction should stop so that the harvest does not run forever Dec 20, 2023

block.call(document)
rescue StandardError => e
e
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to do something with e?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not at the moment. We don't have any error reporting yet but once we do we will populate the report with errors :).

@richardmatthewsdev richardmatthewsdev merged commit 194cf33 into main Jan 9, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants