You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
'<' handling is buried deep in .net's built-in System.Xml.XmlReader, so invalid documents can't be parsed without writing a substantial amount of code.
Correcting the input on the fly basically requires writing an own tokenizer which seems quite excessive for something as simple as ignoring an opening bracket that should be escaped.
Documentation for XmlParserOptions.IsSuppressingErrors explicitly states, that enabling this option may break the document and it's disabled by default anyway, so changing this behavior won't be an unpleasant surprise for the users.
Currently, trying to parse <condition value="a < b" />would raise an exception even if error suppression is enabled. Proposed change would allow to successfully parse it.
The text was updated successfully, but these errors were encountered:
New Feature Proposal
Description
Allow to bypass opening bracket validation when XmlParserOptions.IsSuppressingErrors is set to true. Just a single-line change
Background
Parsing technically malformed XML-elements that contain opening diamond brackets in attributes.
Currently, trying to parse
<condition value="a < b" />
would raise an exception even if error suppression is enabled. Proposed change would allow to successfully parse it.The text was updated successfully, but these errors were encountered: