Rename folder check

[BKSteve]

Fixes #8720

rework the request for location and add warning message for missing directory

TypeError no longer an issue with this change. (ai comment)

Summary by CodeRabbit

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling for missing show directories, ensuring users are informed about the inability to rename episodes under such circumstances.

[coderabbitai]

Walkthrough

The modification in the home.py file enhances the robustness of the testRename method by introducing a preemptive check for the existence of the show directory. This approach replaces the previous exception handling mechanism, aiming to prevent errors related to missing directories by logging a warning and informing the user about the issue, thus addressing a specific bug that hindered the preview rename functionality.

Changes

File	Change Summary
.../views/home.py	Replaced ShowDirectoryNotFoundException handling with a check for directory existence using os.path.isdir.

Assessment against linked issues

Objective	Addressed	Explanation
Fix the error causing the TypeError in preview rename (#8720)	❌	The changes do not directly address the TypeError issue.
Ensure the rename page loads successfully without a blank screen (#8720)	❌	The changes do not explicitly mention ensuring the successful loading of the rename page.
Investigate and resolve traceback errors in the code (#8720)	❌	There is no specific mention of addressing traceback errors in the summary.

Poem

In the code where bugs like to play,
A rabbit hopped in, brightening the day.
With a flick and a hop, and a gentle nudge,
Fixed a path, without holding a grudge.
🐇 "Fear not," it whispered, with a soft cheer,
"For I'll make your renaming errors disappear."
In the glow of the moon, it danced away,
Leaving behind code that would surely stay.

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: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 3b5a9f4 and 9d7467a.

Files selected for processing (1)

• sickchill/views/home.py (1 hunks)

Files not reviewed due to errors (1)

• (no review received)

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 9d7467a and 5f0e63a.

Files selected for processing (1)

• sickchill/views/home.py (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• sickchill/views/home.py

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 5f0e63a and 4acf862.

Files selected for processing (1)

• sickchill/views/home.py (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• sickchill/views/home.py

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 4acf862 and 2b652a3.

Files selected for processing (1)

• sickchill/views/home.py (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• sickchill/views/home.py