Skip to content

feat: add alucard #15

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat: add alucard #15

wants to merge 1 commit into from

Conversation

luxonauta
Copy link
Member

@luxonauta luxonauta commented Jun 24, 2025

➕ Adds Alucard (Classic) variant according to specs here.

Alucard Preview

@luxonauta luxonauta self-assigned this Jun 24, 2025
Copy link

coderabbitai bot commented Jun 24, 2025

📝 Walkthrough

Walkthrough

A new Xcode color theme file named Alucard.xccolortheme has been added, defining detailed color and font settings for various Xcode UI and syntax elements. The installation instructions in INSTALL.md were reorganized and clarified, with improved separation of installation methods and unified activation steps. Minor formatting changes were made to GitHub template files by adding trailing newlines.

Changes

File(s) Change Summary
.github/issue_template.md,
.github/pull_request_template.md
Added a newline character at the end of each file.
Alucard.xccolortheme Added a new Xcode color theme file with comprehensive color and font settings for UI and syntax.
INSTALL.md Restructured and clarified installation instructions; separated installation methods and unified activation steps.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Repository
    participant Xcode

    User->>Repository: Download or clone theme files (Dracula/Alucard.xccolortheme)
    User->>User: Move theme file to ~/Library/Developer/Xcode/UserData/FontAndColorThemes/
    User->>Xcode: Open Xcode and navigate to Preferences > Themes
    User->>Xcode: Select and activate the new theme
Loading
✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch feat/add-alucard

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@luxonauta luxonauta requested a review from nesl247 June 24, 2025 17:09
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (2)
.github/issue_template.md (1)

1-1: Use “a UI” instead of “an UI”.

Minor grammatical touch-up for smoother reading.

-> If you're reporting an UI issue, make sure you take a screenshot that shows the actual bug.
+> If you're reporting a UI issue, make sure you take a screenshot that shows the actual bug.
INSTALL.md (1)

38-39: Consider updating the theme selection instructions.

The instructions still reference "Dracula Theme" specifically, but with the addition of Alucard, users might expect guidance on selecting either theme variant.

Consider updating the instruction to be more generic:

-2. Select Dracula Theme
+2. Select your preferred theme (Dracula or Alucard)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9b38eef and 2343f4b.

📒 Files selected for processing (4)
  • .github/issue_template.md (1 hunks)
  • .github/pull_request_template.md (1 hunks)
  • Alucard.xccolortheme (1 hunks)
  • INSTALL.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
.github/issue_template.md

[misspelling] ~1-~1: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: > If you're reporting an UI issue, make sure you take a screensh...

(EN_A_VS_AN)

🔇 Additional comments (10)
.github/pull_request_template.md (1)

1-1: LGTM – newline addition keeps templates consistent.
No further action needed.

INSTALL.md (3)

3-9: Excellent addition of Git installation method.

The new Git installation section provides a better way for users to stay updated with theme changes compared to downloading zip files. The clear instructions and logical separation from manual installation improve user experience.


13-13: Good update to use main branch.

Updating the download link to use the main branch instead of master aligns with modern Git conventions and ensures users get the latest version.


24-35: Well-structured theme setup section.

The unified theme setup section effectively consolidates installation steps and properly references both the Dracula and Alucard themes. The separation between Git/Manual installations and all methods provides clear guidance for different installation paths.

Alucard.xccolortheme (6)

1-4: Proper XML structure and DOCTYPE declaration.

The XML declaration and DOCTYPE are correctly formatted for an Xcode color theme plist file, ensuring proper parsing by Xcode.


31-34: Appropriate font and color version settings.

The DVTFontAndColorVersion is set to 1 and DVTLineSpacing to 1.1, which are standard values for Xcode themes.


85-96: Consistent light theme color scheme.

The source text background uses the same warm cream tone as the console background, and the current line highlight, selection, and insertion point colors are well-coordinated for a light theme aesthetic.


98-163: Comprehensive syntax coloring definitions.

The syntax coloring dictionary covers all essential code elements with a consistent color palette. The use of different shades for system vs. user-defined identifiers provides good visual distinction.


164-230: Appropriate font styling for syntax elements.

The font selections are well-thought-out:

  • Regular weight for most identifiers
  • Medium weight for declarations and documentation
  • Bold for keywords and marks
  • MediumItalic for comments

This provides good visual hierarchy while maintaining readability.


1-233: Verify theme completeness and consistency.

The theme appears comprehensive, but it would be good to verify that all necessary Xcode theme keys are included and that the color scheme aligns with the Alucard variant specifications referenced in the PR.

#!/bin/bash
# Verify the theme file structure and check for any missing common Xcode theme keys
echo "Checking theme file structure..."

# Check for common DVT keys that should be present in Xcode themes
expected_keys=(
    "DVTConsoleDebuggerInputTextColor"
    "DVTConsoleDebuggerOutputTextColor" 
    "DVTSourceTextBackground"
    "DVTSourceTextSyntaxColors"
    "DVTSourceTextSyntaxFonts"
)

echo "Verifying presence of essential theme keys:"
for key in "${expected_keys[@]}"; do
    if grep -q "$key" Alucard.xccolortheme; then
        echo "$key found"
    else
        echo "$key missing"
    fi
done

# Check color value format (should be RGBA values between 0 and 1)
echo -e "\nChecking for invalid color values..."
grep -E "string>[0-9]+\.[0-9]+ [0-9]+\.[0-9]+ [0-9]+\.[0-9]+ [0-9]+\.[0-9]+<" Alucard.xccolortheme | \
while read -r line; do
    # Extract RGBA values
    rgba=$(echo "$line" | sed -E 's/.*>([0-9.]+) ([0-9.]+) ([0-9.]+) ([0-9.]+)<.*/\1 \2 \3 \4/')
    for value in $rgba; do
        if (( $(echo "$value > 1.0" | bc -l) )); then
            echo "⚠ Potential invalid color value: $value in line: $line"
        fi
    done
done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant