Introduced new error on latest PR merges.

[WardVandevoort]

Hi Chris,

Thank you for merging my PR. I decided to switch back from my fork to your dev-master, however I noticed you introduced a new error during your merges. In the ProductFormFeature there are now 2 use cases at the top of the file for CodeList220 (see: https://github.com/chrisribal/onix-parser/blob/3c62367a5fad9e5404e43324d3662c64213ee8bd/src/Product/ProductFormFeature.php#LL8C37-L8C37). This causes a Fatal Compile Error so could you please fix this?

Thx,
Ward

[danwholegrain]

Hi @WardVandevoort / @chrisribal

I'm getting a fatal error that seems to be stemming from using multiple types for the ProductFormFeature.

See https://github.com/commonknowledge/onix-parser/blob/078db8c3336607f2b8d1bd822a223c84e6008953/src/Product/ProductFormFeature.php#L50

What I'm seeing... When a code that should be looked up from CodeList98 (FCO) exists in the XML from ProductFormFeatureValue, the parser is attempting to look up from CodeList220 and throwing a fatal error because it doesn't exist there. If I switch around the order of the type hinting (CodeList98 | CodeList220) it's working fine, so potentially because the data mapping is looking at the first type (CodeList220) only.

Any thoughts on resolving appreciated 🙏