Open matthewhorridge opened 2 months ago
To add context: this is present when a field or element is added to a template or element. We wanted to make a clear distinction of what properties belong to the child artifact itself (which will be present if the child artifact is serialized as a first-class entity), and which properties are deployment information, only possible when a field or element is included as a child
E.g. we have,
Why do I have to nest these things inside a configuration object? Why not at the top level for a child?