Check XML files for well-formedness #1271
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Test FAILed. |
| let xmlHasErrors = false; | ||
| let DomParser = require("xmldom").DOMParser; | ||
| sourceFiles | ||
| .filter(file => _.endsWith(file, ".xml")) |
|
Nice one! 👍 |
teobugslayer
force-pushed
the
totev/xml-verify
branch
from
6564ef8 to
c3af46f
Compare
|
Test PASSed. |
teobugslayer
added a commit
that referenced
this pull request
Nov 27, 2015
Check XML files for well-formedness
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Check XML files for well-formedness. No validation is performed. The check should happen at least on build and livesync.
Whenever an invalid XML file is found:
Implementation detail: it happens actually on prepare.
See #1272