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

New: Lists retroactively apply tags #10537

Open
wants to merge 12 commits into
base: develop
Choose a base branch
from

Conversation

scphantm
Copy link
Contributor

@scphantm scphantm commented Oct 7, 2024

Database Migration

YES - 241

Description

This request gives the import lists system the ability to retroactively apply tags to existing movies in the database.

Screenshot (if UI related)

Todos

  • Tests
  • Translation Keys (./src/NzbDrone.Core/Localization/Core/en.json)
  • Wiki Updates

Issues Fixed or Closed by this PR

  • Fixes #XXXX

Willie Slepecki added 2 commits October 4, 2024 13:47
This commit introduces a new feature allowing tags to be retroactively applied to movies already in the database. Changes include database migration for the new column, updates to the frontend to manage this feature, and backend logic to handle retroactive tagging.
Moved and added translations for retroactive tag application. Corrected minor organizational issues in the JSON file to maintain consistency.
@github-actions github-actions bot added Area: UI Issue is related to UI, should also add the issue to the new UI project, if it isn't a bug. Area: API Issue is related to the API Area: Import Lists Issue is related to Importing from Lists Area: Db-migration Warning: DB Migration | Related to DB Migration labels Oct 7, 2024
@scphantm
Copy link
Contributor Author

scphantm commented Oct 7, 2024

I got this working. Still not sure how to unit test it, and need to keep looking to see if i missed any documentation

This addresses issue #10507

@scphantm
Copy link
Contributor Author

scphantm commented Oct 7, 2024

Fixes #5299

@scphantm
Copy link
Contributor Author

scphantm commented Oct 7, 2024

fixes #6464

moving to another PR
configured to auto-detect if building on an ARM mac or not
@scphantm
Copy link
Contributor Author

scphantm commented Oct 8, 2024

It doesn't look like there are any wiki pages that would need to be updated. please correct if i am wrong, i added the columns to the two modal screens.

Enhanced the migration script to include the RetroApplyTags column for the Notifications and Indexers tables, ensuring consistent data structure across related tables. This column is added with a default value of 0, similar to the ImportLists table.
Changed the RetroApplyTags column type in ImportLists to Boolean. Added RetroApplyTags column to Notifications, Indexers, and DownloadClients with a default value of false. This ensures consistent behavior across these tables.
@mynameisbogdan mynameisbogdan added the Status: Don't Merge Hold up - don't merge this label Oct 9, 2024
@scphantm
Copy link
Contributor Author

Yea I'm rethinking this solution a little bit. I hate adding those 3 additional columns just cuz I added a field. I'm going to look at the interfaces harder and see if I can come up with a better way.

@scphantm
Copy link
Contributor Author

When/If i figure out a way to remove those unneeded fields, is there anything else that causes alarm here? I'd really like to get this submitted. There's another feature request i wanted to work on this would be integrated with.

Removed the RetroApplyTags field from ProviderDefinition, Notifications, Indexers, DownloadClients, and relevant API resources. RetroApplyTags is now exclusively managed within ImportListDefinition.
The RetroApplyTags property has been removed to streamline the ProviderResource class. This change will help to reduce unnecessary attributes, simplifying the overall codebase.
@github-actions github-actions bot removed the Area: API Issue is related to the API label Oct 13, 2024
This change introduces a new boolean field called retroApplyTags to the Radarr API V3. It ensures that the API schema includes this property for any relevant operations. This helps in handling retroactive tag application within the system.
@github-actions github-actions bot added the Area: API Issue is related to the API label Oct 13, 2024
The retroApplyTags property was deleted to streamline the API schema. This change ensures the JSON specification is more concise and easier to maintain.
@github-actions github-actions bot removed the Area: API Issue is related to the API label Oct 13, 2024
@scphantm
Copy link
Contributor Author

What else needs completed to merge this?

@bakerboy448 bakerboy448 changed the title Feature/retro add tags New: Lists retroactively apply tags Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Db-migration Warning: DB Migration | Related to DB Migration Area: Import Lists Issue is related to Importing from Lists Area: UI Issue is related to UI, should also add the issue to the new UI project, if it isn't a bug. Status: Don't Merge Hold up - don't merge this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants