type: Allow 'omitempty' on DPC types

[rucoder]

EVE now uses 'omitempty' on all fields inside DPC structure that breaks deserilization. We use

#[derive(Default)]
#[serde(default)] 
struct type {
}

on then and to allow missing fields.

We do not care about omitting fileds with default values when we serialize DPC because IPC transport has no limit on message size

[uncleDecart]

When we receive value which is omitted, we would assume default value for it, do we want to differentiate it somehow? I.e. wrapping around Optional, would this behavior be troublesome

[uncleDecart]

LGTM

only one comment regarding the behavior

[rucoder]

When we receive value which is omitted, we would assume default value for it, do we want to differentiate it somehow? I.e. wrapping around Optional, would this behavior be troublesome

@uncleDecart
it has nothing to do with Option, it is exactly Default, so value is ALWAYS there , just default . Option means : value may be absent at all - no value