-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new tests for syntax and ill-formed parser errors and fix... emm... errors #684
Merged
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
fa5783c
Add a method to enable or disable all well-formedness checks
Mingun 81811c6
Replace `Error::XmlDeclWithoutVersion` by `Error::IllFormed(MissedVer…
Mingun 3eada71
Replace `Error::EmptyDocType` by `Error::IllFormed(MissedDoctypeName)`
Mingun d3bd2d4
Add explicit integration tests for syntax errors
Mingun 6e4636b
Fix position reporting of unclosed SyntaxErrors - now they always poi…
Mingun 2e50e5c
Parse `<??>` as syntactically valid processing instruction
Mingun 0b76169
Parse `<?xml?>` as XML declaration instead of processing instruction
Mingun 141a950
Add explicit integration tests for ill-formed errors
Mingun 187149b
Fix incorrect position reported for `Error::IllFormed(DoubleHyphenInC…
Mingun d4d9f5f
Fix incorrect position reported for `Error::IllFormed(MissedDoctypeNa…
Mingun 55039e8
Rewrite MissedDoctypeName check to be more obvious
Mingun 2c55638
Rename IllFormed errors based on feedback
Mingun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you intend to leave these names as
missed_doctype_name3
(and below,mismatched_end1
, anddouble_hyphen_in_comment1
) for testing variants that are well-formed?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The main motivation is that these names of the "test about
MissedDoctypeName
error number one... number two... and so on". The final test is a canary test that ensures that after all we able to parse correct representation without mentioned error.I could wrap that tests into module named
missed_doctype_name
(snake cased error name), but I decide, that indent level would be not very comfort. The similar names of tests for the particular error is useful for running of only related tests viacargo test ... -- missed_doctype_name
.In the end, I thought that just a common name with a number is quite convenient and concise.