Relates to #1420 but can be done standalone.
The IUnknownPropertiesConsumer implementation today is different than expected, we can either fix it or remove it as the 'unknown' map that this implementation generates is usually dropped during ingestion.
Not all protocol classes accept non-mapped fields, but we implement IUnknownPropertiesConsumer for every protocol class, this should also be addressed.
It's not a high priority issue though because it only affects hybrid SDKs or when one downgrade the SDK and has a cached envelope that has now a field that is unknown.
Relates to #1420 but can be done standalone.
The
IUnknownPropertiesConsumerimplementation today is different than expected, we can either fix it or remove it as the 'unknown' map that this implementation generates is usually dropped during ingestion.Not all protocol classes accept non-mapped fields, but we implement
IUnknownPropertiesConsumerfor every protocol class, this should also be addressed.It's not a high priority issue though because it only affects hybrid SDKs or when one downgrade the SDK and has a cached envelope that has now a field that is unknown.