As new element type - Custom element - was added to Delivery output, it's needed to add its support to SDKs.
Actually, it's already added to .NET SDK and code generator
Custom element stores its value as simple string. The format of the string is free and determined by the developer who creates element.
In Delivery output custom element has type "custom"
It should be supported in generator as well.
Proposed solution
The concrete solution depends on concrete SDK implementation.
Generally, you should add Custom Element into list of supported types with type name "custom" and data type "string".
Also you should add Custom element type into tests.
Motivation
As new element type - Custom element - was added to Delivery output, it's needed to add its support to SDKs. Actually, it's already added to .NET SDK and code generator
Custom element stores its value as simple string. The format of the string is free and determined by the developer who creates element.
In Delivery output custom element has type "custom"
It should be supported in generator as well.
Proposed solution
The concrete solution depends on concrete SDK implementation. Generally, you should add Custom Element into list of supported types with type name "custom" and data type "string". Also you should add Custom element type into tests.
Additional context
An example of Delivery output with Custom element
{
}