CS 1.0: SD-2246: Remove empty parameters list

[HenrikHL]

User description

[SD-2246[(https://dcsa.atlassian.net/browse/SD-2246): Remove empty parameters list on root level

---

PR Type

Enhancement

---

Description

• Remove empty parameters list from OpenAPI specification

• Eliminates redundant empty array declarations in path definitions

• Improves YAML specification clarity and maintainability

---

Diagram Walkthrough

flowchart LR
  A["OpenAPI YAML<br/>with empty parameters"] -- "Remove redundant<br/>empty arrays" --> B["Cleaner OpenAPI<br/>specification"]

Loading

File Walkthrough

	Relevant files
Enhancement	CS_v1.0.2.yaml Remove empty parameters arrays from API paths                        cs/v1/CS_v1.0.2.yaml Removed empty parameters: [] declaration from /v1/port-schedules path Removed empty parameters: [] declaration from /v1/vessel-schedules path Eliminates unnecessary empty parameter arrays that add no functional value +0/-2

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.