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
I'm currently using the language service for doing some validation of xml, specifically for invalid xml like the following:
<badTag>event-1 missing an end tag
<badTag>event-1</badTag end tag missing a closing '>'
<badTag/ self closing tag missing a closing '>'
these all work just fine right now, I can use LanguageService.parseHTMLDocument and it'll return a document where those nodes have been parsed and I can then check them to see if they're missing something.
However one case doesn't get returned as a node from the parse function and that's this
bagTag> content </badTag> the first tag is missing it's opening '<', but also there's a closing tag without an opening tag.
is this something that could be fixed? is there another way I should go about validating this html with the language service? I'm using the parsed document for doing a lot of other analysis of the xml so I don't want to just use the scanner as that would be a fair bit of duplicate work, but I'm not sure how else I would go about catching this corner case.
The text was updated successfully, but these errors were encountered:
I'm currently using the language service for doing some validation of xml, specifically for invalid xml like the following:
<badTag>event-1
missing an end tag<badTag>event-1</badTag
end tag missing a closing '>'<badTag/
self closing tag missing a closing '>'these all work just fine right now, I can use
LanguageService.parseHTMLDocument
and it'll return a document where those nodes have been parsed and I can then check them to see if they're missing something.However one case doesn't get returned as a node from the parse function and that's this
bagTag> content </badTag>
the first tag is missing it's opening '<', but also there's a closing tag without an opening tag.is this something that could be fixed? is there another way I should go about validating this html with the language service? I'm using the parsed document for doing a lot of other analysis of the xml so I don't want to just use the scanner as that would be a fair bit of duplicate work, but I'm not sure how else I would go about catching this corner case.
The text was updated successfully, but these errors were encountered: