Mass Update-Edit revert mako changes until properly fixed

[BKSteve]

Re-enables mass Edit under mass Update.
Will require further future action to improve code but this gets it working again.

Summary by CodeRabbit

• Refactor
  • Improved the accuracy of dropdown selections in the mass edit page for quality presets, episode statuses, show types, and word preferences, enhancing the user interface experience.

[coderabbitai]

Walkthrough

The updates to the manage_massEdit.mako file focus on refining the dropdown menu selections within the user interface. By adjusting the conditional logic for the selected attribute, these changes ensure that various settings such as quality presets, episode statuses, show types, and word preferences are accurately reflected in the UI. This enhances the user experience by ensuring consistency between user settings and their representations.

Changes

File Path	Change Summary
.../gui/slick/views/manage_massEdit.mako	Updated selection options in dropdown menus by refining conditional logic for the selected attribute.

🐇✨
In the code's warren, deep and vast,
A change was made, not the first, not the last.
Dropdowns now smart, with logic so keen,
Reflecting choices, on the screen so clean.
🌟🐾

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ccabea6 and db30830.

Files selected for processing (1)

• sickchill/gui/slick/views/manage_massEdit.mako (14 hunks)

Additional comments: 14

sickchill/gui/slick/views/manage_massEdit.mako (14)

• 100-100: The conditional for setting an option as 'selected' based on quality_value is correct. However, consider verifying that quality_value is always an integer and not a string to avoid unexpected behavior.
• 111-111: The logic for selecting 'Allowed' qualities appears correct. Ensure that anyQualities correctly contains all qualities that should be marked as selected.
• 121-121: Similar to the 'Allowed' qualities, ensure that bestQualities correctly reflects the preferred qualities to be marked as selected.
• 139-141: The conditional logic for selecting 'Yes' or 'No' based on season_folders_value is correct. Ensure that season_folders_value is always an integer to match the expected values (1 for 'Yes', 0 for 'No').
• 153-155: The logic for setting the 'Paused' dropdown selection is correct. Verify that paused_value is properly sourced and sanitized before this point to prevent any unexpected selections.
• 169-169: Ensure that the logic for setting the default episode status based on default_ep_status_value correctly reflects the intended behavior and that default_ep_status_value is always an integer.
• 182-184: The conditional logic for 'Scene Numbering' selection is correct. Confirm that scene_value is correctly assigned and sanitized upstream.
• 196-198: The logic for setting the 'Anime' dropdown selection based on anime_value is correct. Ensure that anime_value is always an integer to match the expected values.
• 212-214: The conditional logic for the 'Sports' selection is correct. Verify that sports_value is properly managed and sanitized before this point.
• 235-237: The logic for setting the 'Air by date' selection is correct. Confirm that air_by_date_value is correctly assigned and sanitized upstream.
• 256-258: The logic for setting the 'Subtitles' selection is correct. Ensure that subtitles_value is always an integer to match the expected values.
• 270-272: The logic for setting the 'Ignored Words' selection seems correct. However, verify the intended behavior for 'New' and 'Clear' options and ensure ignore_words_value is correctly managed.
• 287-289: The logic for setting the 'Preferred Words' selection is correct. Confirm that prefer_words_value is correctly assigned and sanitized upstream.
• 304-306: The logic for setting the 'Required Words' selection is correct. Ensure that require_words_value is always an integer to match the expected values.