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

Adding the reprocess update type. #154

Conversation

THOR300
Copy link
Collaborator

@THOR300 THOR300 commented Dec 9, 2024

Description

Adds reprocess as an update type. This is desired as we want to perform the parse action in the ingest stage as outlined below. It would seem confusing to then set the Update type as SOURCE_URL to trigger reprocessing so adding as a new type.

update_type_actions = {
    UpdateTypes.SOURCE_URL: parse,
    UpdateTypes.NAME: update_dont_parse,
    UpdateTypes.DESCRIPTION: update_dont_parse,
    UpdateTypes.METADATA: update_dont_parse,
    UpdateTypes.SLUG: update_field_in_all_occurences,
    UpdateTypes.REPARSE: reparse,
}

Also adds the document update config block to hold data like:

DocUpdateConfig(reparse_updates=["cclw.doc.0.1", "cclw.doc.0.2", ...])

Proposed version

Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

  • Skip auto-tagging
  • Patch
  • Minor version
  • Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.

Notes:

  • If none of these options are selected, auto-tagging will fail (integrated soon)
  • Where multiple options are selected, the most senior option ticked will be
    used -- e.g. Major > Minor > Patch
  • If you are selecting the version in the list above using the textbox, make
    sure your selected option is marked [x] with no spaces in between the
    brackets and the x

Type of change

Please select the option(s) below that are most relevant:

  • Bug fix
  • New feature
  • Breaking change

How Has This Been Tested?

Please describe the tests that you added to verify your changes.

Before submitting

  • I've read and followed all steps in the Making a pull request
    section of the CONTRIBUTING docs.
  • I've updated or added any relevant docstrings following the syntax described in the
    Writing docstrings section of the CONTRIBUTING docs.
  • If this PR fixes a bug, I've added a test that will fail without my fix.
  • If this PR adds a new feature, I've added tests that sufficiently cover my new functionality.

Copy link

linear bot commented Dec 9, 2024

@THOR300 THOR300 marked this pull request as ready for review December 9, 2024 10:53
@THOR300 THOR300 requested a review from a team as a code owner December 9, 2024 10:53
@THOR300 THOR300 merged commit 8b5f905 into main Dec 9, 2024
6 checks passed
@THOR300 THOR300 deleted the feature/pla-328-implement-reprocess-functionality-into-identify-updates branch December 9, 2024 12:00
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.

2 participants