html5ever
html5ever copied to clipboard
Move code generation into an integration test
Since the generated code only depends on files in the repository anyway, save the separate compilation for the build script and only generate code in a test. Make it fail if the generated code is different from the stored source code to make CI fail if the generated code is out of date.
If this is deemed useful, we can do a similar thing for the maps generated in markup5ever.
Ping?
:umbrella: The latest upstream changes (presumably #481) made this pull request unmergeable. Please resolve the merge conflicts.
Another ping... @nox did you want to take a look?
:umbrella: The latest upstream changes (presumably #491) made this pull request unmergeable. Please resolve the merge conflicts.
@jdm if I rebase this, will you review it?
Rebased.
@jdm since you seem to be paying attention -- got an opinion on this?
One other reason I prefer this approach is that the generated code becomes much more legible (for example, via the IDE). I was trying to clean up extern crate usage and ended up creating issues in the generated code, which were pretty hard to inspect.