Tracks: https://github.com/konveyor/tackle2-ui/issues/2284

Summary

Since platform awareness requires the ability to attach a dynamic set of fields to at least a platform entity, being able to handle a set schema defined fields is required.

New Work

From a json-schema associated to an entity through an entity type (e.g. Source platform coordinates through the platform's type), we need to be able to support:

• Display of a schema
• View a document with a schema via patternfly components
• View a document with a schema via the @patternfly/react-code-editor
• Edit a document with a schema via patternfly components
• Edit a complex document with a schema via the @patternfly/react-code-editor
• Know when to choose the patternfly render/edit vs the react-code-editor render/edit (probably based on schema complexity)
• 🤔 Allow the user to select the render/edit view

Note: This is similar to how OCP Console handles entities at various points – some as form fields, some as the yaml document.