Avoid using DerivedElement with known elements for mixed wildcards

[tefra]

📒 Description

xsdata is always wrapping data models with the DerivedElement generic during data binding.

There were multiple limitations with the generator and the resolve all qualified names.

I am not sure when but these issues are currently resolved so it's time to drop the mandatory wrapping to only when it's necessary.

Resolves #693 and #437

🔗 What I've Done

• Update parsing to check mixed elements for a known qname
• Update serializer to check for a known qname for mixed objects

💬 Comments

This breaks backwards compatibility. People will need to check object instance type and not assume it will always be a DerivedElement

🛫 Checklist

• Updated docs
• Added unit-tests
• Sample tests pass
• W3C tests pass

[codecov]

Codecov Report

Merging #696 (2325be6) into master (9f646da) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #696   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           99        99           
  Lines         8688      8691    +3     
  Branches      2194      2195    +1     
=========================================
+ Hits          8688      8691    +3     

Impacted Files	Coverage Δ
xsdata/formats/dataclass/parsers/nodes/element.py	100.00% <100.00%> (ø)
xsdata/formats/dataclass/serializers/xml.py	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication