Skip to content

Conversation

@fizikiukas
Copy link
Contributor

@fizikiukas fizikiukas commented Dec 2, 2025

Summary by CodeRabbit

Release Notes

  • New Features
    • Added DNS resource support to Hostinger API integration
    • Expanded Docker operations for VPS: create/delete projects, manage containers, view logs, restart/start/stop projects, and more
    • Added contact management operations: list, create, and delete contacts; manage contact groups

✏️ Tip: You can customize this high-level summary in your review settings.

@fizikiukas fizikiukas requested a review from a team as a code owner December 2, 2025 09:59
@coderabbitai
Copy link

coderabbitai bot commented Dec 2, 2025

📝 Walkthrough

Walkthrough

The Hostinger API node configuration is enhanced with new resource and operation options. A DNS resource option is added, followed by 10 Docker-related operations for the vpsDocker resource and 4 contact management operations for the reach resource.

Changes

Cohort / File(s) Summary
Hostinger API Node Configuration
nodes/hostingerApi/HostingerApi.node.ts
Added DNS resource option. Extended vpsDocker resource operations with 10 Docker project and container management actions (createProject, deleteProject, getLogs, listContainers, listContents, listProjects, restartProject, startProject, stopProject, updateProject). Extended reach resource operations with 4 contact management actions (listContacts, createContact, deleteContact, listContactGroups).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • Verify all new operation options are correctly named and have appropriate action descriptions
  • Confirm consistency of naming conventions across Docker and contact-related operations
  • Check for any potential duplicates or conflicts with existing operations

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is vague and generic, using version numbering without describing what changes or improvements the PR introduces. Revise the title to describe the actual changes, such as 'Add DNS resource and Docker/Reach operations to Hostinger API node' to clearly communicate the main improvements.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/release-v.1.0.12

Comment @coderabbitai help to get the list of available commands and usage tips.

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

🧹 Nitpick comments (1)
nodes/hostingerApi/HostingerApi.node.ts (1)

43-44: Consider fixing the resource name instead of suppressing the lint rule.

The eslint-disable-next-line comment for node-param-resource-with-plural-option suggests that "DNS" violates n8n's naming conventions for resources. Rather than suppressing the lint rule, consider renaming the resource to follow conventions—for example, "DNS Records" or "DNS Zones" (depending on what the operations actually manage).

Example fix:

-// eslint-disable-next-line n8n-nodes-base/node-param-resource-with-plural-option
-{ name: 'DNS', value: 'dns', },
+{ name: 'DNS Zones', value: 'dns', },
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 225acc5 and b5c3801.

📒 Files selected for processing (1)
  • nodes/hostingerApi/HostingerApi.node.ts (3 hunks)

@fizikiukas fizikiukas merged commit 0350eca into main Dec 2, 2025
1 check passed
@fizikiukas fizikiukas deleted the fix/release-v.1.0.12 branch December 2, 2025 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants