Leonidas-from-XIV / node-xml2js / 273

98%

Pull #317

travis-ci

Preserve Children Order in case of mixed content.

In current functionality, in order to maintain Chilren Order in case if mixed content like this:

<TailParas fid="td">
	<Para>That capitulation reflects the conundrum facing Mr. Ballmer's successor, <En cat="pe" fpRef="958861" instRef="7" djRef="9589153">Satya Nadella</En>, who took over two years ago, as he runs out of options to bolster <En cat="co" fpRef="27147355" instRef="8" djRef="mcrost">Microsoft</En>'s standing in mobile technology. His new strategy aims to help information-technology managers cope with the increasingly central position of smartphones in corporate networks. The company is betting that corporate customers will want to use <En cat="co" fpRef="27147355" instRef="9" djRef="mcrost">Microsoft</En>'s technology to lock down and control devices on their networks.</Para>
	<Para>In a statement, Mr. Nadella also touted its Continuum feature, which enables a smartphone running Windows 10 to function as a surrogate PC when connected to a monitor and keyboard.</Para>
	<Para>
		<En cat="co" fpRef="27147355" instRef="10" djRef="mcrost">Microsoft</En> must establish its Windows operating system on a substantial portion of smartphones or accept a diminished presence in the technology landscape, where mobile devices outnumber personal computers—and it may not get another chance, said Forrester Research Inc. analyst Julie Ask.</Para>
</TailParas>

you need to pass these flags: 
explicitChildren: true, preserveChildrenOrder : true, charsAsChildren: true, includeWhiteChars: true
And these flag generates lots of extraneous json nodes.

With this change I have added a flag called preserveChildrenOrderForMixedContent (default is false). But if it's turned on, it will generate following output. Basically, it's smart enough to detect that it has mixed content and will wrap the object only if required in order to maintain the order.

{
  "$": {
    "fid": "td"
  },
  "Para": [
    {... (continued)

68 of 68 new or added lines in 1 file covered. (100.0%)

364 of 375 relevant lines covered (97.07%)

1233.0 hits per line