feat(scrapers): allow cloning of existing dockets #5867
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.
Currently,
clone_from_cl
crashes if you try to clone a docket that already exists in the database. So if you want to pull in new docket entries and documents for a docket, you have to manually delete all of the docket's existing entries and documents. This is the minimal amount of changes required (read: fast and dirty) to allow a docket's entries to be updated. I've used it a number of times and it's been very useful.While this works great, I am going to do a larger rewrite of
clone_from_cl
to simplify the logic and make updates much more efficient. So I have a few questions (and feel free to move this to an Issue or Discussion):I think my approach would be to only add new objects and add a
--force
option that would update everything.