Compile the set as the PDF generator does - #56
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Lambda Feedback makes PDFs with lambda-feedback/PDF-generator (cloned at ../pdf-generator): pandoc with src/template.latex and xelatex. Text that pipeline rejects is a fault in the set. Add a validate check that compiles the whole set once through the same template and engine and maps errors back to fields by line. xelatex is optional like Node: without it validate says what to install, and CI installs the same TeX collection the generator's Dockerfile does. Done when a set with a known LaTeX fault in one field reports that field, and the clean test data compiles.
Workbench ticket t30.