Fix json output when a node with attributes has the same key several times #245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some XML nodes have the same key multiple times. If the sub node have attributes, only the last key is keeped.
I adapted the code that managed nodes without attributes to manage those with.
The event "Microsoft-Windows-CertificateServicesClient-Lifecycle-System/Operational 1007" with the "EKU" node show the case.
Before the fix
After the fix: