feat: let users type custom ports manually

[hcavarsan]

Changes

• Added custom port option to port selector dropdown
• Added input field that appears when custom port is selected

relates #351

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• .github/workflows/main.yml is excluded by !**/*.yml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes introduce a new constant CUSTOM_PORT in the AddConfigModal component to enhance port configuration flexibility. The modification allows users to select a custom port option when configuring remote connections. When the custom port is selected, the component dynamically switches between a select dropdown and a direct input field, enabling more flexible port configuration for users.

Changes

File	Change Summary
frontend/src/components/AddConfigModal/index.tsx	- Added CUSTOM_PORT constant with value -1 and label "Custom Port..." - Modified handleSelectChange to handle custom port selection - Updated rendering logic to show custom port input when needed

Sequence Diagram

sequenceDiagram
    participant User
    participant AddConfigModal
    participant PortSelection

    User->>AddConfigModal: Open Modal
    AddConfigModal->>PortSelection: Display Port Options
    User->>PortSelection: Select Port Option
    alt Custom Port Selected
        PortSelection->>AddConfigModal: Trigger Custom Port Input
        User->>AddConfigModal: Enter Custom Port
    else Standard Port Selected
        PortSelection->>AddConfigModal: Set Port Value
    end

Loading

---

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>, please review it.
  • Generate unit testing code for this file.
  • 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 generate unit testing code 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 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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

frontend/src/components/AddConfigModal/index.tsx (1)

50-53: Consider using an enum for port constants.

The CUSTOM_PORT constant could be part of an enum to better manage special port values and improve type safety.

-  const CUSTOM_PORT = {
-    value: -1,
-    label: 'Custom Port...',
-  } as const
+  enum PortType {
+    CUSTOM = -1
+  }
+
+  const CUSTOM_PORT = {
+    value: PortType.CUSTOM,
+    label: 'Custom Port...',
+  } as const

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1879ea6 and e2d7d30.

⛔ Files ignored due to path filters (1)

• package.json is excluded by !**/*.json

📒 Files selected for processing (1)

• frontend/src/components/AddConfigModal/index.tsx (4 hunks)

🧰 Additional context used

🪛 Biome (1.9.4)

frontend/src/components/AddConfigModal/index.tsx

[error] 766-766: isNaN is unsafe. It attempts a type coercion. Use Number.isNaN instead.

See the MDN documentation for more details.
Unsafe fix: Use Number.isNaN instead.

(lint/suspicious/noGlobalIsNan)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build-and-push-docker
• GitHub Check: Clippy

🔇 Additional comments (1)

frontend/src/components/AddConfigModal/index.tsx (1)

428-433: LGTM: Port options array modification.

The port options array is correctly modified to handle the custom port option.