Add MessageQueue to CronTabItemTriggerType enum

[adenchen123]

User description

The CronTabItemTriggerType enum now includes a new value, MessageQueue, which was added after the existing OpenAPI value.

---

PR Type

Enhancement

---

Description

• Add MessageQueue value to CronTabItemTriggerType enum

• Extends trigger type support for cron tab items

---

Diagram Walkthrough

flowchart LR
  A["CronTabItemTriggerType enum"] -- "adds new value" --> B["MessageQueue"]
  A -- "existing values" --> C["BackgroundWatcher, OpenAPI"]

Loading

File Walkthrough

	Relevant files
Enhancement	CrontabItem.cs Add MessageQueue enum value to trigger type                            src/Infrastructure/BotSharp.Abstraction/Crontab/Models/CrontabItem.cs Added MessageQueue enum value to CronTabItemTriggerType Positioned after existing OpenAPI value Enables message queue as a trigger type for cron tab items +2/-1

---

[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: 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
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Auditing Context: The new enum values introduce a new trigger type but do not include or reference audit logging of critical actions, which may be handled elsewhere and thus cannot be fully verified from this diff alone. Referred Code public enum CronTabItemTriggerType { BackgroundWatcher, OpenAPI, MessageQueue } Learn more about managing compliance generic rules or creating your own custom rules

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.