fix: reorder options for clarity and consistency

[fizikiukas]

Summary by CodeRabbit

• Refactor
  • Reorganized the ordering of operation options in Reach configuration. All available operations remain functional with default behavior unchanged.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The Reach operation options in the Hostinger API node were reordered, moving List Contacts and List Segments entries to the end of the options array. Functionality and default selection remain unchanged.

Changes

Cohort / File(s)	Summary
Operation options reordering nodes/hostingerApi/HostingerApi.node.ts	Reordered Reach operation options: moved List Contacts and List Segments from their original position to the end of the array

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify the reordering is intentional and doesn't break any option selection logic
• Confirm the default option (listContacts) remains functional after reordering

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: reorder options for clarity and consistency' accurately describes the main change: reordering operation options in the HostingerApi node for improved clarity and consistency.
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/lint

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

nodes/hostingerApi/HostingerApi.node.ts (1)

420-423: Reconsider placing the default option first.

The default operation is listContacts (line 425), but it's now positioned near the end of the dropdown. Standard UX practice places default options first for better visibility and user expectation. Consider either:

• Moving "List Contacts" back to the first position, or
• Changing the default to a more contextually appropriate operation if "List Contacts" shouldn't be the primary action

</review_comment_end>

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1679ec1 and 784ed10.

📒 Files selected for processing (1)

• nodes/hostingerApi/HostingerApi.node.ts (1 hunks)