Treating Designs as an abstraction, applying DRY

[leecalcote]

Current Behavior

Designs are declarations (see Contributing to Mehery Models for a definition of what a declaration is) and are largely abstracts amalgamating existing component and relationship definitions into a document.

Desired Behavior

In doing so, Designs should avoid recreating / redefining properties of existing Meshery resources.

Implementation

1. Includes $refComponent and $refRelationship.
2. Make “components” an array of $refComponents (

   schemas/schemas/constructs/v1beta1/designs.json

   Lines 22 to 26 in a7561a7

   	"description": "Map of component instances to their corresponding component declarations",
   	"additionalProperties": {
   	"type": "string",
   	"format": "uuid"
   	},

   )

---

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