Skip to content

runtime.Unstructured support for Scheme.Convert #944

@matthiasbruns

Description

@matthiasbruns

Description

We currently do not support Unstructured in Schema.Convert - there was a quick attempt here open-component-model/open-component-model@6309a5d#diff-4b40a5b3380086b2fa158745f5feaffb60c2af308fa97ce7654a21451a4e5485R428 but we should spend more time doing it right.

We stumble across this usually when we want to support our complete type-system to be parsed into a concrete type.

scheme.Convert should support Unstructured as a source and concrete types as a target. We would have to use the internal type field in the json payload as the type to parse into, and then use the internal json data as the content of the type. You can check how raw does it, scheme.Convert needs a comparable handling for Unstructured.

Done Criteria

  • Schema.Convert supports Unstructured as source and target
  • Code has been reviewed by other team members
  • Analysis of existing tests (Unit and Integration)
  • Unit Tests created for new code or existing Unit Tests updated
  • Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
  • Enduser Documentation updated (if applicable)
  • Internal technical Documentation created/updated (if applicable)
  • Successful demonstration in Review

Metadata

Metadata

Assignees

Labels

area/ipceiImportant Project of Common European Interestkind/tasksmall task, normally part of feature or epic

Type

No fields configured for Task.

Projects

Status
📋 Next-UP

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions