Catalog schema: Proposal to shift classes from enum to oneof type string

[leecalcote]

Current Behavior

Regarding this discussion, meshery/meshkit#542 (comment), the current approach to having Catalog content class descriptions in a separate, single property makes extraction of the enum value and its corresponding description a bit more challenging than is perhaps necessary.

Proposal:

{
    "type": "string",
    "oneOf": [
        { "const": "open", "description": "The issue is currently open." },
        { "const": "closed", "description": "The issue has been resolved." },
        { "const": "pending" } // Waiting for more information
    ]
}

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.