Feature Request: Add configuration to allow unknown/custom XML fields #331
Description
We are currently integrating with a Prime Broker that uses custom XML tags not defined in the standard schema. Currently, the library rejects these messages due to unknown fields.
To support integrations with non-standard providers, I suggest introducing a configuration flag: validate_user_defined_fields (or ignore_unknown_fields).
With default as current strict validation; throw an error if an unknown tag is encountered.