Closed stloyd closed 1 month ago
Results of the benchmarks from this PR are compared with the results from 1.x branch.
I would simply remove DOMNodeEntry and replace it with DOMElementEntry, I fucked up a bit at the beginning not reading properly definition of DOMNode which can be anything, including the attribute, DOMElement is what I was actually thinking about but since it wasn't usable I don't think it's a huge BC Break.
About attributes, I think it should be handled out of the scope of this PR since it's more XMLWriter responsibility rather than DOMElementEntry to convert entries into elements/attributes.
\Flow\ETL\Function\XPath
you might need to look into this one as well since it returns DOMNode which is later converted by the native entry factory into DOMNodeEntry but I think it should be pretty straightforward to cast it into DOMElement. Afaik it's the only scalar function that operates on XML.
Change Log
Added
Fixed
Changed
Removed
Deprecated
Security
Description
Using simply just
DOMNode
generates problems as we're unable to work with XML attributes, which are available on a class that extendsDOMNode
=DOMElement
.