Skip to content

improving the looks and docs of network-vpn #346

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

Merged
merged 1 commit into from
Jun 25, 2025

Conversation

Theoreticallyhugo
Copy link
Collaborator

No description provided.

Copy link

coderabbitai bot commented Jun 25, 2025

📝 Walkthrough

Walkthrough

The documentation for the network-vpn widget was updated to clarify its functionality, especially regarding Tailscale exit node support and output customization. The associated script was modified to allow configurable output formatting based on a verbosity flag, enabling users to display either a label or a label with the VPN IP address.

Changes

File(s) Change Summary
docs/CONFIG.md Updated widget documentation: clarified behavior, added Tailscale details, instructions, and an example.
scripts/network_vpn.sh Modified output: added verbosity-based conditional formatting and label customization for VPN status.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant network_vpn.sh
    participant System (tun0 interface)

    User->>network_vpn.sh: Run script with (or without) verbose flag
    network_vpn.sh->>System (tun0 interface): Check for VPN IP
    alt VPN IP detected
        alt Verbose mode enabled
            network_vpn.sh->>User: Output label + VPN IP address
        else Verbose mode disabled
            network_vpn.sh->>User: Output label only
        end
    else No VPN IP detected
        network_vpn.sh->>User: (No VPN output)
    end
Loading
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch feat/vpn-prettify

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.

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

🧹 Nitpick comments (2)
docs/CONFIG.md (1)

518-529: Tighten wording and fix macOS casing/apostrophe issues

Minor copy-editing will make this paragraph read more professionally:

-This widget tries to display whether a vpn is connected.
-Tailscale exit nodes are fully supported for Linux and MacOS.
-
-Set verbose to true in order to see the VPNs IP or name of Tailscale exit node.
+This widget tries to display whether a VPN is connected.
+Tailscale exit nodes are fully supported on Linux and macOS.
+
+Set `@dracula-network-vpn-verbose` to `true` to see the VPN’s IP address or the
+name of the Tailscale exit node.

Besides the grammar tweaks (VPN’s, macOS, avoid “in order to”), this keeps terminology and option names consistent with the neighbouring examples.

scripts/network_vpn.sh (1)

23-29: Remove duplication by fetching the label once

get_tmux_option is executed twice even though the option value never changes inside the branch. A tiny refactor improves readability and avoids an extra tmux call:

-      if $verbose; then
-        vpn_label=$(get_tmux_option "@dracula-network-vpn-label" "󰌘 ")
-        echo "$vpn_label$vpn"
-      else
-        vpn_label=$(get_tmux_option "@dracula-network-vpn-label" "VPN-ON")
-        echo "$vpn_label"
-      fi
+      vpn_label=$(get_tmux_option "@dracula-network-vpn-label" "󰌘 ")
+      if $verbose; then
+        echo "${vpn_label}${vpn}"
+      else
+        echo "${vpn_label}"
+      fi

(The default icon is preserved; users can still override it via the option.)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3323120 and 15c3699.

📒 Files selected for processing (2)
  • docs/CONFIG.md (1 hunks)
  • scripts/network_vpn.sh (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/CONFIG.md

[grammar] ~519-~519: The operating system from Apple is written “macOS”.
Context: ...nodes are fully supported for Linux and MacOS. Set verbose to true in order to see t...

(MAC_OS)


[style] ~521-~521: Consider a more concise word here.
Context: ...r Linux and MacOS. Set verbose to true in order to see the VPNs IP or name of Tailscale ex...

(IN_ORDER_TO_PREMIUM)

@Theoreticallyhugo Theoreticallyhugo merged commit 0e568d1 into master Jun 25, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant